Shit Happens – Achieve Extensibility
summary
Describes building an event-driven layer where the order service only emits an OrdersPlaced event while email, SMS and loyalty consumers subscribe independently. Shows using in-memory events for tests and moving to RabbitMQ or Kafka in production, using MassTransit to wire messaging, and running consumers as serverless functions or containers on Kubernetes. Emphasizes documenting each event producer and consumer to reduce coupling and improve scalability.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 5:40Business events
- 9:13Event-driven architecture
- 17:50Designing event system
- 24:20Separate consumer processes
- 31:09Scaling with Kafka and cloud
- 33:36Cloud event services
- 37:09Summary and Q&A
related talks
56mEvents on the outside, on the inside and at the core
44mThe Dark Side of Events
30mHow Event Driven Architectures Go Wrong & How to Fix Them
57mSimplify Your Architecture: Events and Publishing
39mEvents, Workflows, Sagas? Keep Your Event-driven Architecture Sane.
48m9 Fallacies of Event driven Architectures
01h 04mDDDamn good!
49mRethinking Reactive Architectures