4 ms·
Seems like a fundamental misunderstanding to me. Commands get validated via your aggregate, not events. Events are not allowed to be rejected. Ever. Because the
by randolorian 5y ago
Seems like a fundamental misunderstanding to me. Commands get validated via your aggregate, not events. Events are not allowed to be rejected. Ever. Because they already happened.
- EdwardDiego 5y agoThinking that event sourcing and CQRS are synonyms is a fundamental misunderstanding also. Anyway, pedantry aside, my point remains thus - it's hard to prevent invalid state transitions being submitted to an event sourcing datastore, and when devs can submit events directly, then these invalid transitions will occur.
- randolorian 5y ago> Thinking that event sourcing and CQRS are synonyms is a fundamental misunderstanding also. Indeed. These are two separate patterns. They can have great synergy when used together but it's not a requirement. > it's hard to prevent invalid state transitions being submitted to an event sourcing datastore Apply DDD, use code review, and use stream level ACLs.