A routine ANALYZE flipped a Postgres query plan from an index scan to a sequential scan, and our API went from 12ms to 8 seconds. Here's what we learned about a failure mode most teams never think about.
- Published On
Hello, I'm Luke
Personal blog about my experiences and thoughts on software development.
Latest Posts
- A client moved their reads to database replicas for performance. The latency numbers looked great — until customers started getting charged twice and inventory counts drifted from reality.
- Published On
- A client found one of their API keys in a public error log. Tracing where that key actually lived took longer than fixing the leak — and revealed a secrets management problem nobody wanted to own.
- Published On
- A client's payment provider was sending webhook notifications correctly. Their system acknowledged every one. And then quietly threw most of them away.
- Published On
- A client's "graceful degradation" strategy silently served stale pricing data for 11 hours. The outage would have been better.
- Published On