Domain-Driven Design Community

That's not the only alternative. Since it isn't clear whether this concept of "project priority" is an entity, then instead come at it the other direction, by

That kind of leads me to believe the service is the right approach. If it smells fishy to create some kind of aggegate to handle this concept, maybe the old

The UL should support your business domain model. You should not be trying to find how you fit into DDD, but rather how DDD can facilitate your business needs.

I mentioned this before...ProjectPriorityList is likely a value object on some other entity. You really don't care about the identity of a

This brings up a question I had. The concept of a ProjectPriority list seems like a viable solution at first, but i'm not sure its a valid DDD principle. In my

I'm moving in that direction. I have done bits and pieces of the asynchronous model described by Udi before with out realizing it. After watching the

If you already have the separation between the web application and your service where I'm assuming Rhino Service Bus is running then what you described would

ok, now I got it! As I'm thinking through all this I'm thinking of the tools i currently use in some form or another (monorail, windsor, rhino.servicebus,

Hi Jason, Since the query part is typically a separate denormalized store (whether in the same table or another table in the same database or even a separate

Eben, what do you mean by 100% consistency vs. eventual consistency?

You don't happen to have the presentation slides available in PDF form, do you? Thanks, Pat

Hello Jason, You have to remember that Udi will probably not prepare a talk for the trivial cases :) In any event. In my previous project we had a similar

The way Greg makes it seem, you have to separate the theory of CQRS from the all the goodness that goes along with it: event sourcing, eventual consistency,

That would make sense, finding what part work for a given situation is the key.

So why don't have you have a ProjectPriority list then? And has been pointed out, implementing as a linked list makes the reordering trivial. Pat

The main thing about that presentation is the *why* behind CQRS, so that it doesn't end up getting used where it doesn't make sense. That being said, there are

The link is in the original post.

Have some video of his presentation? ... -- []'s Gustavo Melo

I watched Udi's presentation on CQRS this week.

Hi, In our case, Objects are fetched from the Reporting Model through a Query. CustomerContactInformationReport r =