Moved data and traffic closer to users; cross-region tail latency fell 25% with no consistency regressions.
See the full storyProof of work
The pipeline lost rows quietly under load and we only found out when a customer's numbers didn't add up, which is the worst possible way to find out. I chased it to the root — backpressure, at-least-once handling, and reconciliation that proved nothing fell on the floor rather than hoping it hadn't.
Moved data and traffic closer to users; cross-region tail latency fell 25% with no consistency regressions.
Costs were climbing faster than usage and nobody owned the number, so every team assumed someone else was watching it. I took the problem, instrumented spend down to the service level, and worked through the biggest offenders one at a time until the trend line bent and stayed bent.
Introduced Redis and read replicas behind a clean interface; primary CPU dropped 30%.
Deploys were a held-breath event only a couple of people knew how to do safely, so releases bunched up and got riskier the longer we waited. I made shipping boring — automated the pipeline, put the guardrails in code, and handed the whole team a button they could trust at 5pm on a Friday.
p99 fell from 1200ms to 420ms — a 65% cut sustained through peak traffic.
Ship reliable software that quietly does its job and gets out of the way.
In public
Practical bits
Unlock with a company account to message directly and reveal:
Jump back to the board with this background already filtered in.
