advanced · cohort
Event Streams and Databases
5 weeks · 7 hrs/week
Bridge Kafka-ish thinking with relational invariants. Implement a toy outbox, consume with at-least-once discipline, and write tests that catch double-processing.
What ships in this outline
- Outbox table design lab
- Consumer idempotency keys
- Ordering pitfalls illustrated
- Observability hooks (metrics names only)
- Capstone design doc
Outcomes
- Sketch an outbox schema for a payment adjacency
- List failure modes your consumer tests must cover
- Recommend when to avoid dual writes entirely
Lead mentor
Lin Okada
SRE turned database mentor; previously owned incident reviews for query regressions.
FAQ
We use Redpanda-compatible Docker; concepts generalize.
Consumer examples in Go and TypeScript.
Managed connector marketplaces are not configured step-by-step.
Experience notes
“Outbox lab mirrored our legacy dual-write mess. Tests from week 3 caught a duplicate path we missed.”
“Fast pace — keep buffer on Sundays.”