A good summary. However too many choose to view it only as Event-Sourcing/CQRS, a silver-bullet applicable to a minority of applications. One particularly attra

A good summary. However too many choose to view it only as Event-Sourcing/CQRS, a silver-bullet applicable to a minority of applications. One particularly attractive in Microsoft projects, since it is the only alternative enterprise architecture "practice" they propose to data modeling. Object domain modeling continues to be an anathema, because I think of a wizard and code-generation driven historical perspective. In commercial systems, transactions as actions and events, recorded for business or legal reasons, are central. That includes significant "events" like purchases, sales, reservations etc. In that sense, they all are event driven. Event-Driven as an architecture that is based on recording changes to a baseline state, should be applied only where really suited.