Command Query Responsibility Segregation design pattern

learn more… | top users | synonyms

1
vote
2answers
77 views

Managing non-domain application behaviour in CQRS

Here's a scenario. I am building QueueUnderflow, a community-edited Q&A site for people who haven't yet grasped the basics of data structures. My users don't like it when people edit their posts ...
2
votes
0answers
353 views

How Add/Create* commands should be handled in CQRS + Event Sourcing architecture

I want to implement my first application using CQRS pattern along with Event Sourcing. I am wondering how creation of aggregate roots should be handled properly. Let's say someone sends CreateItem ...
1
vote
0answers
115 views

Entities (DDD) when using CQRS on Akka

When using Akka, CQRS style, is still there a place for Entities? Or does everything now go to Aggregates, implemented as Actors + Value Objects. I notice that most entities are written as mutable ...
0
votes
0answers
29 views

CQRS atop of SOAP component

I'm trying to adapt CQRS in my application. I really like how it simplifies domain model. There is a component with some part of a business logic which is accessible through SOAP. Commands and queries ...
0
votes
0answers
89 views

Event sourcing with a read store - normal relational tables too?

I will be implementing Event Sourcing for the first time on a hobby project and I have what could be a really simple question: should the event store be the only storage area if you have a ...