Start With a Service Class

If your domain has five entities and four screens, a service class is fine. Splitting commands from queries pays back when one class has become the file every change touches, and reads and writes are pulling the same model in different directions.

A typical .NET service starts with one OrderService that has fifteen methods — PlaceOrder, GetOrder, ListOrders, SearchOrders, UpdateShippingAddress, CancelOrder, and so on. Reads and writes share the same domain model. Six months in, the read methods carry six different DTO shapes for six different screens; the write methods carry domain invariants no read needs. Touching one breaks the other. Pull requests block on rebase conflicts in a single 1,400-line file.

🤔 If one service class does everything
Reads and writes have asymmetric requirements. Writes care about invariants, transactions, and concurrency. Reads care about projection shape, latency, and screen-specific data. CQRS — Command/Query Responsibility Segregation — is the simple act of stopping the pretence that they are the same thing.

CQRS is not Event Sourcing. It is not a separate database. It is not even necessarily MediatR. At its smallest, CQRS is “a method either changes state or returns data, never both” (Meyer's Command-Query Separation, lifted up to the responsibility/architectural layer by Greg Young). Everything else — separate read models, separate stores, async projection — is an option you adopt when the workload demands it.