Keynote: The Many Meanings of Event-Driven Architecture

Updated on November 28, 2016
GOTO Chicago 2017
Martin Fowler
Martin Fowler

Author, speaker, consultant and general loud-mouth on software development

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.)