Event Driven Collaboration

on YouTube ↗49m

" summary

Explains why distributed service data must be treated as data on the inside vs data on the outside and gives two concrete integration patterns: either emit enriched document messages that carry all fields downstream, or populate local caches via event-carried state transfer so consumers read locally. Covers choreography vs orchestration (sagas), correctness fixes: outbox pattern, log‑tailing and broker‑driven retry, and why append‑only logs (Kafka) support replay and compacted caches better than transient queues.

AI-written summary · about

" chapters (14)

1. 0:00Introduction
2. 1:58BrighterSeeing
3. 2:51Agenda
4. 8:16SOA
5. 15:46Cache
6. 17:19Join Problem
7. 22:39Events
8. 26:00Document Message
9. 27:11Pipes and Filters
10. 31:51Reference Data
11. 36:12Information References
12. 39:08Quick Rules
13. 40:44Correctness
14. 45:07Logs vs Keys

" related talks

• 57mEvent Driven CollaborationIan Cooper · NDC Oslo 2019
• 57mEvent Driven CollaborationIan Cooper · Highload fwdays'20
• 31mDemystifying Event-Driven ArchitecturesBogdan Sucaciu · Conf42 Enterprise Software 2021
• 48mEvent-Driven Architecture – Benefits and PitfallsRamanan Natarajan · Developer Summit 2020
• 53mPatterns of Event Driven ArchitectureMark Richards · Great International Developer Summit 2023
• 47mEvent-Driven Microservices = Microservices Done RightUrs Peter · J-Fall 2022
• 51mComplex Event Flows in Distributed SystemsBernd Rücker · DevConf 2018
• 46mEvent-Driven Microservices - not (just) about Events!Allard Buijze · GOTO Berlin 2018