Event Driven Collaboration
summary
Argues that moving from request-driven to receiver-driven flow control succeeds when teams adopt concrete patterns: use the outbox pattern to avoid lost events, apply event-carried state transfer so services have local read caches, prefer a message log like Kafka for catch-up and a shared-queue like RabbitMQ for notifications, and handle reservations with timed retries and idempotent consumers. Results: increased independent deployability and resilience, at the cost of added operational complexity and harder observability.
AI-written summary · about
chapters (4)
related talks
57mEvent Driven Collaboration
49mEvent Driven Collaboration
47mEvent-Driven Microservices = Microservices Done Right
53mPatterns of Event Driven Architecture
31mDemystifying Event-Driven Architectures
51mComplex Event Flows in Distributed Systems
52mSo You Want to Build An Event Driven System?
48mEvent-Driven Architecture – Benefits and Pitfalls