Designing a mission critical event system
summary
Design covers a concrete fintech case: events must reach accounting within one minute so losses and support costs stay tiny. Implementation uses a transactional outbox to make DB writes and event emission atomic, RabbitMQ for delivery while migrating to GCP and evaluating Kafka, and a UUID idempotency key + unique-index guard to guarantee at-most-once effects on consumers. Delivery latency, processing time and consumer lag go to metrics and SLAs with alerts so breaches surface before customers notice.
AI-written summary · about
chapters (8)
- 0:00Introduction to event systems
- 2:52Defining the event architecture
- 5:46Business context at Molly
- 9:06Setting design capabilities
- 10:27Ensuring reliable delivery
- 17:31Idempotency and processing
- 22:15Observability and monitoring
- 25:52Conclusion and takeaways
related talks
30mUnhappy Path & Dealing with Bad Events
55mAvoiding mistakes with events, one event at a time
39mArchitectural design patterns applied to Distributed Systems
55mAn Introduction to Enterprise Design Events
51mComplex Event Flows in Distributed Systems
59mBuilding resilient event-driven architectures
15mCompliance-by-Construction for Credit Apps
31mUsing Telemetry in Cloud Native Applications