Folks,
I am working on a model where users can choose defaults or enter custom values, the results form a number of population-based projections.
I am drawn to using a CQRS-like approach to separate reporting and domain-affecting code.
I intend to use basic SQL views with ADO.NET in one service for reports, and Entity Framework in another service for persisting modifications.
I don’t think that event sourcing is required here. Reporting will be done against the domain database.
Is the above an example of CQRS?
It is not fully CQRS but it is a good practices from CQRS to bring into your DDD solution, i blogged exactly about this topic with example here
You take the concept of separating read from write model to make ur domain more solid, but without the complexity of separating database and event storage.