There's only one issue here. Taking the Fowler's definition as the source of truth lead to misunderstanding the pattern itself, and, as the result, to an implementation, which has little to nothing to do with Event Sourcing. Fowler's definition describes whatever, but not Event Sourcing. In two words, Event Sourcing is the way to persist the system state as events, which represent state transitions, rather than state itself. Distributing events to other systems for them to do whatever (materialised views, integrations, etc) is EDA (event-driven architecture). It is completely orthogonal to Event Sourcing. Event Sourcing indeed makes EDA easier to bring in, so it can be seen as an enabler. One can do EDA without Event Sourcing, which this article clearly demonstrates. However, it is not about Event Sourcing.