Moved data and traffic closer to users; cross-region tail latency fell 40% with no consistency regressions.
See the full storyProof of work
We had outgrown a single region but the code still assumed the world was one datacenter, so latency for half our users was quietly terrible. I led the move to multi-region — sorted out data locality and consistency, and kept the failure modes something we could actually reason about.
Moved data and traffic closer to users; cross-region tail latency fell 40% with no consistency regressions.
Two teams were blocked on the same shared bottleneck and each was waiting for the other to move first. I designed the contract between them and the migration path to reach it, so both could ship on their own schedule instead of renegotiating scope at every release.
Decomposed the monolith behind a strangler proxy into 3 services — no maintenance window needed.
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.
Introduced Redis and read replicas behind a clean interface; primary CPU dropped 15%.
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.
Sharded the pipeline and tuned batching; throughput held at 9k events/sec at steady state.
Bring craft and measurement to work that usually gets neither.
Off the clock
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.
