Chapter 2Separating Read and Write Models
Now that you’ve started your event sourcing journey by learning about aggregates and building simple examples, next, you’ll learn about another building block, which involves separating an application’s read and write models. The concept of separating the read model from the write model is nothing new. Databases have supported views as a separate read model since the dawn of time, allowing the creation of customized sets of data designed to answer specific queries. Sometimes this is just a shortcut for another query, while other times a materialized view (such as a denormalized table or even a simple key-value store) stores a totally separate copy of data in anticipation of queries.
The concept of materialized ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access