Hello Sam, Now this is just typical! Users want everything and it seems a mess. Now the question is: why do they want it? I would venture a guess. They want...
Hi Bert, Thanks for your quick reply. Yes I am aware of the challenge in the physical data model, more specifically, in how to efficiency store/load/search...
Hi Sam, I'd be happy to discuss this more with you in person but I know the problem space reasonably well through Stefan. I might consider a radical departure...
Hello, OK... so a buddy of mine reckons that task / domain service processes should be on the actual entity else the entity is simply a container. Putting the...
Hi Sean ! I'm not sure if the specification pattern is the right way to go. If our customer is adding new discounts dynamically, how do you connect these new...
After thinking about it I believe you are correct. I am going to play around with the possibility of adding discounts dynamically from the client, but even...
Putting the processes on the entity would, of course, require the entity to access repositories and have access to other tasks and stuff. Well there are many...
... Well, you might consider another specification that can work from dynamically-added discounts -- however you get dynamicism (dynamic languages, rule...
Hey everyone, @Greg, maybe define the differences between a domain service and an application service. I would think an application probably has more to do...
I am currently trying to implement a proper domain model and got to the issue of exceptions and who is responsible for throwing these, types etc. I am...
First of all, are you sure that "logging in" actually belongs in your Domain layer? Users and authentication seem like more of an Application concern to me...
Hey guys, I'm looking for some guidance on handling persistence via repositories when using the Party Roles pattern. Specifically, I have a core assembly which...
Hi there, I have been busy reading Jimmys book and Erics book and a lot of websites out there and I am still confused as to the role of services and where they...
Yeah, I've seen a lot of confusion about services. As far as I'm concerned (and other people may have other viewpoints), services are things that the domain ...
Hi John, you are probably talking about a application service. That one must not be confused with a domain service, the one Eric talks about. A service in that...
Hi Andrew, like I wrote to John: the services Eric talks about are parts of the domain model. They are equivalent to entities and value objects but their ...
btw: Every conceptual discussion (and every concept) has many opinions that could be POSSIBLY right. That's the nature of concepts ;-) But my opinion is that...
When reading the DDD book, or talking to Eric, understand that when he talks about DDD he isn't necessarily talking about the Domain Model Pattern. Also, keep...
Great clarification udi. There is nothing wrong with simpler patterns in such situations, in fact I would generally prefer them Greg ... -- Sent from Gmail for...
Ja, you see... Now this is what I was thinking. If there are entities that do not have behaviour it is what it is. They are not aneamic by design --- there is...
On the other hand, I'm thinking the domain service to be a business logic handler that can be largely extended. For example, the credit service listed in...
Hey guys, I realized that I posted this question at a really bad time (thursday afternoon before a long weekend), and that it probably wouldn't stand a very...
Respectfully, I disagree that services should be avoided. Services play a critical role in DDD: they act as the boundary between the domain and applications....
