Hi, I wondered if any one could help me out and point the DD way for me? I have an interesting - though I doubt uncommon - problem: aggregates are formed from...
This is a known problem for all federated data access. That doesn't make it any simpler of course, I know. The best practices I have been applying to this in...
I'll admit that there is a lot to digest and some stuff is stretching me a little so can I start with I understand this as...? So, if I understand this right...
Yes you got it right. You could make life a little easier by 'folding' your toplevel customer repository and your federation service into one class - I don't...
Cheers Bert - I'm glad I'm running on the right tracks! How about we stretch this a stage further and treat each provider as it's own domain. Then the federal...
Hi Ron, This is a relatively interesting framework-ish question that doesn't come up very often. I think there can be advantage in extracting common behaviors...
I realize this is a rather old topic, but I'm having a similar problem and none of the solutions suggested in the thread seem to solve my issue. In my case,...
Hmm, not sure why you would say you shouldn't have a Tracks collection. In option 2 you can retrieve tracks based on a name from an album. However, what if you...
Looks good to me. Personally I would not expose the versioning mechanism in a separate repository. Similar to how you must work with object identifiers and ...
I'm positively certain the music industry views tracks as independently navigable entities. Just check the ratio of new album releases versus compilations.... ...
What about when value objects have to be loaded from infrastructure? For example an order form requires a form country to post to. A drop down list of Country...
As country is an attribute of the order, I think it would be best to manipulate the country value through the order repository. And for populating drop down...
I wrote a requirements doc and a design doc that I can share - those are both relatively free of technology. In my daytime job I do not code myself so I cannot...
This comes up all the time in my world. For the majority of processing, something like Album is a good choice for an aggregate root so I model the system that...
Nick, Given that there is a use case where you search for Tracks based on some criteria, I would model the relation between Track and Album as bidirectional...
I agree; aggregate identification is influenced as much by interaction design as by existence dependencies. Randy ________________________________ From:...
I have come to the same conclusion and it makes life much easier. Look at all your information as a tangled web of associations. You should be able to start...
Value Objects and Exceptions leaking out of the Domain Layer Hi, I've been reading DDD lately and have a question about layers' boundaries: Is it safe to let...
This topic came up once before but there wasn't much of an answer: http://tech.groups.yahoo.com/group/domaindrivendesign/message/4425 The answer was that AOP...
Hi, You can probably use the GoF Decorator Pattern in order to simulate AOP on your services... To put it in a nutshell, this pattern is pretty much like...
I'm tackling a variant of this for a client, which is simpler in some ways and possibly harder in others. Their legacy system has a database with natural keys...
Depending on what you are trying to achieve, giving up the DDD approach in this particular scenario doesn't sound like a bad idea - the piece of the app that...
Sorry for replaying so lately. I have installed Vista, and I have been busy setting things up. I don't have a good place for the design documents you...
Hello! For some time I have been thinking on the following two sentence: "Yet another approach for querying is to use the Specification pattern" ... "Even...
Hello! Before I begin I would like to say that I don't know if it is the right group to post this question, but I have found it difficult to find a better...
