Code Review
Reviewing the Timeout That Was Longer Than the Caller's
The service waited ten seconds for its dependency while the caller gave up after five, so the work continued for an audience that had left, and the caller's…
Code Review
The service waited ten seconds for its dependency while the caller gave up after five, so the work continued for an audience that had left, and the caller's…
Ecommerce
The support tool had no idempotency key and the operator clicked again after a slow response, so the customer was refunded twice, and the ledger showed one…
Error Autopsy
The client retried on its own schedule instead of the server's, so the backoff was shorter than the throttle window, and the account stayed limited long…
Security
The limiter keyed on the connection address, and behind the proxy that address was the load balancer, so the whole office shared one bucket, and one user…
Code Review
The request had no timeout and no cancellation, so the abandoned navigation left the fetch running, and the response wrote to a component that no longer…
DevOps
The nightly export ran longer than its interval one evening, so two instances ran at once and both wrote to the same output file, and the file was half of…
Code Review
The client retried the failed payment request on a timeout, and the original had succeeded, so the retry charged the customer a second time for one order…
DevOps
The rollback reverted both changes at once, so the fix for the prompt also undid the model upgrade, and the incident lasted until someone split the two and…
Opinion
When the model is unavailable the feature should still do something useful, and an apology message is not a fallback, it is an outage with better copy, and…
DevOps
The model version floated, the provider shipped an update, and the JSON the parser expected gained a wrapper, so every request parsed to empty and nothing…
Ecommerce
A draft order reserves inventory the moment it is created, and the reservation outlives the draft, so abandoned drafts held stock for days, and the…
DevOps
AWS confirmed in September that data held exclusively in me-south-1 and mec1-az2 cannot be restored. Multi-AZ worked as designed.