Event Driven Collaboration

on YouTube ↗57m

" summary

Explains how moving from shared databases to per-service ownership forces distributed data and how switching from request-driven to receiver-driven flow reduces chatty calls and uptime coupling. Shows concrete patterns: event-carried state transfer for building local caches of account and product data, the outbox pattern to guarantee at-least-once delivery, log‑tailing as an alternative, and choreography versus orchestration for sagas. Includes examples and libraries in C#, Python and Go and demos using RabbitMQ and Kafka.

AI-written summary · about

" chapters (14)

1. 0:00Introduction to collaboration
2. 2:42Agenda and SOA evolution
3. 3:52Data inside vs outside
4. 7:42Microservice boundaries
5. 10:59Data outside service
6. 14:40Request vs event-driven
7. 20:23Handling temporal coupling
8. 22:00Choreography vs orchestration
9. 25:58Managing complex workflows
10. 28:44Event carried state transfer
11. 37:00Reference data patterns
12. 40:44Ensuring data correctness
13. 46:48Log tailing and messaging
14. 52:19Data composition and closing

" related talks

• 57mEvent Driven CollaborationIan Cooper · Highload fwdays'20
• 49mEvent Driven CollaborationIan Cooper · Build Stuff 2019
• 47mEvent-Driven Microservices = Microservices Done RightUrs Peter · J-Fall 2022
• 31mDemystifying Event-Driven ArchitecturesBogdan Sucaciu · Conf42 Enterprise Software 2021
• 48mEvent-Driven Architecture – Benefits and PitfallsRamanan Natarajan · Developer Summit 2020
• 51mComplex Event Flows in Distributed SystemsBernd Rücker · DevConf 2018
• 01h 08mEvent Driven Architecture – Enabling MicroservicesBrad Irby · Silicon Valley Code Camp 2018
• 51mPatterns & Practices of Implementing Event-driven MicroSvc...Nikhil Barthwal · GeeCON Prague 2023