Part 1 of 7 · 1 min read
Why this page comes fourth
In this module you will
- Tell an event from a command and say when each becomes a fact.
- Compare orchestration with choreography for a business process that spans services.
- Explain event sourcing: store what happened, derive the current state by replaying it.
- Explain CQRS and build more than one read model from one event log.
- Describe the main costs: delayed read models, harder tracing, and the difficulty of deleting data.
Pages 1 to 3 explained how messages move. This page asks what the messages should say and what a system looks like when it is organised around them. It prepares the next two pages, which process events in bulk (batch) and as they arrive (streams). The books used are "Designing Data-Intensive Applications" (DDIA), "Building Microservices" and "Fundamentals of Software Architecture". The numbers are made up to show the idea, unless the text names a book.