CTRL ALTSCtrl Alt Solvereal-world developer knowledge
SearchJoin
Ctrl Alt Solve — Don't just ask what to do. Learn what developers experienced when they did it.

Search

Find people and experiences by name, username, role/title, keyword, or technology tag.

Popular tags

#postgres#queues#redis#observability#sre#opentelemetry#networking#career#nginx#leadership#debugging#nextjs#edge#auth#billing#migration#architecture#typescript#api#dx#webhooks#testing#ci#slack
6 posts tagged #data-exports
Career3d ago·1 entry

we hit with data exports during a traffic spike

We ran into this around data exports during a traffic spike. Retries arrived out of order and our fixtures only modeled the happy path. Sleeping in tests hid the races and slowed CI. Replaying a small set of recorded payloads found the idempotency bug. We asserted on stored keys, not on elapsed time. The suite is shorter and finally recreates the incident we cared about.

0 views0 likes0 comments0 bookmarks
#data exports
SSuresh Babu
Read →
Case study4d ago·1 entry

we handled data exports after we split the monolith

We ran into this around data exports after we split the monolith. We needed a lock so two workers would not process the same job. One option expired itself. The other lived next to our source of truth. Failover behavior mattered more than the benchmark. We started with the store we could operate, then moved the hot path later. Pick the tool your on-call can reason about.

0 views0 likes0 comments0 bookmarks
#data exports
NNaveen Kumar
Career5d ago·1 entry

we hit with data exports while rolling back payments

We ran into this around data exports while rolling back payments. Retries arrived out of order and our fixtures only modeled the happy path. Sleeping in tests hid the races and slowed CI. Replaying a small set of recorded payloads found the idempotency bug. We asserted on stored keys, not on elapsed time. The suite is shorter and finally recreates the incident we cared about.

0 views0 likes0 comments0 bookmarks
#data exports
EEthan Brooks
Case study6d ago·1 entry

we handled data exports on a quiet Sunday incident

We ran into this around data exports on a quiet Sunday incident. We needed a lock so two workers would not process the same job. One option expired itself. The other lived next to our source of truth. Failover behavior mattered more than the benchmark. We started with the store we could operate, then moved the hot path later. Pick the tool your on-call can reason about.

0 views0 likes0 comments0 bookmarks
#data exports
RRitika Malhotra
Career7d ago·1 entry

we hit with data exports after the replica failover

We ran into this around data exports after the replica failover. Retries arrived out of order and our fixtures only modeled the happy path. Sleeping in tests hid the races and slowed CI. Replaying a small set of recorded payloads found the idempotency bug. We asserted on stored keys, not on elapsed time. The suite is shorter and finally recreates the incident we cared about.

0 views0 likes0 comments0 bookmarks
#data exports
RRohit Shekar
Case study9d ago·1 entry

we handled data exports during a Friday deploy

We ran into this around data exports during a Friday deploy. We needed a lock so two workers would not process the same job. One option expired itself. The other lived next to our source of truth. Failover behavior mattered more than the benchmark. We started with the store we could operate, then moved the hot path later. Pick the tool your on-call can reason about.

0 views0 likes0 comments0 bookmarks
#data exports
GGanesh Iyer
Read →
Read →
Read →
Read →
Read →