Train like the backend engineer you're becoming.
01 pick a project 02 build on your machine 03 break it, then document
By signing in you agree to the privacy policy.
$ make up
✓ the system comes up as it runs in production
✓ the load generator is ready
# then, on purpose:
Send the same charge body twice with one idempotency key and inspect both responses and the charge list.
- D1 Both responses describe the same charge, and the second request does not create a new charge.
- D2 The storm produces one charge for the key and reports zero duplicate charges.
- D3 The second request returns a conflict and the original charge remains the only charge for that key.
record what happened, then write it up
Real systems. One project at a time.
The payment that happened twice
A mobile timeout made one customer pay twice. Make retries safe without hiding a changed request behind the same key.
The reports that slowed Tuesday
A new report filter turned Tuesday's p99 into a customer wait. Find the evidence, fix the query path, and prove the number comes back.
The quota that multiplied
Three API instances quietly gave every client three quotas. Replace the local counter with one shared window and keep clients informed when to retry.
The orders that never reached the warehouse
BrasaCart accepted orders that vanished between checkout and the warehouse; make the handoff survive a broker outage and a repeated delivery.
Twice the shipping email
A worker restart made RotaSul send the same shipping notice twice; trace the delivery, fix the invariant, and prove the count is zero.
The API nobody could see inside
LumeCasa discovered a catalog outage through customer tickets; make the service explain itself and page before the next incident spreads.
The checkout prices that vanished after a deploy
A deploy emptied Mira's price cache and a burst of shoppers overwhelmed the store; make cold reads safe, measurable, and useful during a Redis outage.
The notification queue that made OTPs wait
Bellbird's newsletter backlog made one-time codes wait while providers failed and throttled; separate urgency from delivery risk and prove the result.
The wallet that spent the same credit twice
Hearth's wallet allowed one customer to spend the same credit twice; reproduce the negative balance, rule out the slow PSP, and restore the invariant.
Nothing matches that filter yet.