Command Query Responsibility Segregation design pattern

learn more… | top users | synonyms

1
vote
2answers
226 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 ...
1
vote
1answer
143 views

Domain Driven Design - designing Aggregate Roots

Imagine you're designing an application for organizing Workshops. Workshop itself is quite complicated - it acts as a state machine with multiple possible states and transitions between them. We're ...
0
votes
1answer
51 views

Sharing data between bounded contexts

I'm developing a tournament management system that uses a mixture of CQRS/ES/DDD and basic CRUD. I've defined 2 bounded contexts so far: TeamManagement and TournamentManagement. The TeamManagement ...
2
votes
0answers
566 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
114 views

How shall I project CQRS command and query services through WCF

I got directed to this site for more conceptual questions. Here is my issue: Im designing an application that uses CQRS to expose functionality to higher levels in the stack. This looks like below ...
0
votes
0answers
152 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 ...