System Design
Event Backbone Design Intensive
Model domains as streams without painting yourself into an operational corner.
Overview
For teams adopting or refining event-driven patterns. Topics include idempotency keys, poison message handling, and observability that respects human attention spans.
Included
- Sketch sessions for bounded event vocabularies
- Tabletop failure injections for broker outages
- Guidance on ordering guarantees without over-promising
- Templates for replay procedures
- Office hours on schema evolution
- Checklist for cross-org workflow handoffs
- Lightweight metrics for consumer lag storytelling
Outcomes
- Document ordering guarantees your team will not regret.
- List three operational metrics tied to human response times.
- Draft a replay runbook section stakeholders can skim.
Lead contact
Haneul Park
Former platform lead for a Seoul-based logistics SaaS; now coaches architecture cohorts across APAC.
FAQ
Kafka-only?
Examples lean on log-based brokers but patterns map to other implementations.
Exactly-once claims?
We debunk sloppy marketing language and settle on engineering-precise phrases.
Limitations?
No vendor sales pitches or benchmark bake-offs.
Recent notes
“Poison message tabletop felt uncomfortably realistic—in a productive way. Replay template is in our repo now.”