Why is whole system event sourcing an anti-pattern?

Question

I\'m currently designing a new enterprise system. The system\'s purpose is to track, display, and notify employees of customer\'s interactions (i.e. events) with the company

Answer 1

The article cites a talk by Greg Young. The relevant section is viewable here.

Young explains that CRUD hides "all kinds of crazy use cases", and gives correcting typos as an example.

He also points out that analysis can be more expensive in an event-sourced system.

In general, having immutable events as the source of truth for a given part of a system, separated from read models, carries costs and should not be adopted blindly.

Young suggests that "something more like event-driven" would be a top-level architecture rather than CQRS/event sourcing.