Lessons
1A successful request is not the invariant60 min read
Trace a duplicate reservation and design one durable operation record.
- →Define a business invariant and its transaction boundary
- →Distinguish operation identity from request identity
2Read the schedule before selecting isolation35 min read
Compare a lost update with a cross-row invariant and select a valid control.
- →Prevent concurrent write anomalies
3A committed order needs a durable next step35 min read
Close the database-to-message gap and explain duplicate delivery.
- →Connect committed data to durable events
- →Design idempotent consumers
4Recover an unknown external outcome35 min read
Write a recovery table for a payment request whose response is lost.
- →Explain recovery from an unknown external outcome
Skills in this course
- 01Define a business invariant and its transaction boundaryDefine a business invariant and its transaction boundary.
- 02Distinguish operation identity from request identityDistinguish operation identity from request identity.
- 03Prevent concurrent write anomaliesPrevent concurrent write anomalies.
- 04Connect committed data to durable eventsConnect committed data to durable events.
- 05Design idempotent consumersDesign idempotent consumers.
- 06Explain recovery from an unknown external outcomeExplain recovery from an unknown external outcome.