Day 14 of 14 40 minDesignSimulateFailure drills
Put the whole course together. Design the topics, keys and services for an online shop, run the system on the simulator, then break it on purpose (a crashed service, failed brokers, a poison message and a late new service) and watch the design hold up.
By the end of today you can
- Design topics, keys and consumer groups for an event-driven system
- Trace one order through several services
- Show that at-least-once delivery plus idempotent services prevents double charges
- Show that replication with acks=all survives broker failures
- Use a dead-letter topic and replay history for a new service
What's inside
- 7 sections
- 2 diagrams and mind maps
- 5 code examples you can run
- 5-question quiz
- 1The design
- 2Run the happy path
- 3Drill 1: a service crashes
- 4Drill 2: brokers fail
- 5Drill 3: a poison order
- 6Drill 4: a new service joins late
- 7What you've built
Sign in free to read this lesson
Get the full lesson with diagrams, runnable code and the quiz. Your progress is saved across devices.
Sign in free