Command-Query Responsibility Segregation (CQRS) is an architectural pattern which separates commands (that change the data) from queries (that read the data).
Can anyone give me examples of how in production a correlation id can be used? I have read it is …
rabbitmq message-queue nservicebus amqp cqrsMy team has been "tasked" to create an application that follows the task-based UI (not necessarily with CQRS). I really …
user-interface domain-driven-design cqrsI have been reading about using Command objects to represent use cases that our domain exposes, and Command Handler objects …
design-patterns domain-driven-design cqrs command-patternI am trying to build an xUnit Test project for an MVC Core 2.2 Application that is based on the CQRS/…
cqrs mediatrBesides missing some of the benefits of Event Sourcing, are there any other drawbacks to adapting an existing architecture to …
cqrs event-sourcing ncqrsIn CQRS, do they Commands and Queries belong in the Domain? Do the Events also belong in the Domain? If …
domain-driven-design cqrsI'm trying to follow this post by Jimmy Bogard to implement a mediator pipeline so I can use pre/post …
c# asp.net-web-api2 autofac cqrs mediatrLooking for some suggestions for useful discussion groups, articles, success stories, reference apps, and tooling (.Net) on the subject of …
c# .net cqrs event-sourcingI have been reading about Command Query Responsibility Segregation (CQRS). I sort of wonder how would this work with ASP.…
asp.net-mvc nhibernate orm cqrsI'm trying to understand sagas, and meanwhile I have a specific way of thinking of them - but I am …
aggregate cqrs saga