#Cqrs
4 notas · última:
CQRS Pattern With MediatR
CQRS separates writes from reads so each side can be optimized independently. The text also shows how MediatR can model commands and queries with handlers and a request pipeline.
Don't use MediatR by default on all .NET projects
The text argues that MediatR should not be added by default to every .NET project: the choice depends on the use case, and using internal messaging in dependent contexts can create unnecessary complexity.
DDD, Hexagonal, Onion, Clean, CQRS, … How I put it all together
Herberto Graca explains how he combines Ports & Adapters, Onion, DDD layers, and CQRS into an explicit architecture with inward dependencies, ports, adapters, components, and buses.
DDD, Hexagonal, Onion, Clean, CQRS, … How I put it all together
The post groups Ports & Adapters, Onion, DDD layers, and CQRS into an explicit architecture centered on the application core, with inward-pointing dependencies and decoupled components.