Chapter 11. Implementing CQRS
Computers are useless. They can only give you answers.
—Pablo Picasso
The fundamental aspect of a CQRS solution is the neat separation between the command stack and query stack. This means that each stack is designed separately; such a distinct design potentially can lead to having two distinct domain layers and even two distinct databases.
At the end of the day, there are several different flavors of CQRS.
There are CQRS implementations in which the read domain layer is nearly empty and consists only of plain SQL queries run against the database and data-transfer objects used to carry data up to the presentation layer. In other implementations, you have a read domain model that, overall, looks like a subset of a ...
Get Microsoft .NET: Architecting Applications for the Enterprise, Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
