Keynote: The Many Meanings of Event-Driven Architecture
You need to be signed in to add a collection
During my career, I've often people heard people describe their systems as "event-driven". But when looking deeper that phrase seems to lead to some very different architectural assumptions. On a recent workshop we identified four different patterns which tend to appear under the title of "event-driven": event notification, event-based state transfer, event sourcing, and CQRS. We feel that understanding and using these more precise terms will lead to better communication and decision making. (This talk covers the same ground as [this post](https://martinfowler.com/articles/201701-event-driven.html).)
Transcript
During my career, I've often people heard people describe their systems as "event-driven". But when looking deeper that phrase seems to lead to some very different architectural assumptions. On a recent workshop we identified four different patterns which tend to appear under the title of "event-driven": event notification, event-based state transfer, event sourcing, and CQRS. We feel that understanding and using these more precise terms will lead to better communication and decision making.
(This talk covers the same ground as this post.)
About the speakers
Pioneer of various topics around object-oriented technology and agile methods