The CQRS pattern
In an application, executing commands to read and write data from the data store using the same model or entity is a good approach. This is because managing data is generally easy in programming, and we can also use a scaffold to generate a project. However, when there is a lot of write data present, and the risk of concurrent write operations is high, the need to merge data is more urgent. When we use the same model to execute read and write data, the operation of reading data generally reads all the data within a model, and the operation of writing data generally writes all data in the model. Sometimes, however, we need to write fewer columns of data than there is in the model. In addition, using a single model to read ...
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