less than 1 minute read

People describe their systems as "event-driven". But when looking deeper that phrase seems to lead to some very different architectural assumptions.

This presentation was recorded at GOTO Chicago 2017.
http://gotochgo.com

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.

Read the full abstract here:
http://ift.tt/2q8iJhA