Commands, Events, and Processes
How requested work, accepted facts, queues, projections, and long-running processes change application contracts.
- A Valid Command Can Still Be Refused
- A Command Bus Must Pay for Its Indirection
- A Queued Command Changes the Contract
- CQRS Starts When Reads Need a Different Model
- A Domain Event Is a Fact, Not a Question
- Publishing Events Is Not Event Sourcing
- An Outbox Moves the Failure Window
- A Process Manager Remembers What the Queue Cannot
- Test Process State, Not Message Choreography