The many meanings of event-driven architecture - Martin Fowler https://www.youtube.com/watch?v=STKCRSUsyP0

4 patterns under the name of ‘Event Driven’

  1. Event Notification ./resources/video-the-4-meanings-of-event-driven-architecture-.resources/screenshot.png + reverse coupling + first class + flexibility of adding - no overview in code

events vs commands command: response, I want this to happen

  1. Event-carried State Transfer ./resources/video-the-4-meanings-of-event-driven-architecture-.resources/screenshot.1.png + decoupling + availability no more calls no dependency less calls reduce load - send all needed data - copying of data - eventual consistency

  2. Event Sourcing cf git cf accounting events + snapshots ./resources/video-the-4-meanings-of-event-driven-architecture-.resources/screenshot.2.png alternative state: tweak event on branch, diff state, apply diff memory image: in memory state, no db asynchrony is not required

  3. CQRS

Article which inspired this talk https://martinfowler.com/articles/201701-event-driven.html Article: What do you mean by “Event-Driven”?