Thanks for the insight. Comments inline below, ... [mailto:domaindrivendesign@yahoogroups.com] On Behalf Of vvernon_shiftmethod ... Logical? ... Services....
Hi(Merhaba :) ) Inanc , I had a similar requirement before but Aspecially if you want to generic solution running Specifications both on Database and Memory...
... Great! ... One per BC (model) is typical. Think of it this way: Your BC contains a domain model. Your domain model may or may not be persistent. This is...
Thanks Vaughn That's really helps me figure out how everything in DDD fits together. I understand and have implemented CQS as you've described, the bit I was ...
I usually feel limited for domain model design using DDD/OO techniques due to being coupled to the ORM world. Domain concepts are lost and so not included in...
Okay, thanks for clarifying. So the separate BCs in the case of CQRS are eventually consistent. One is used to store events (Event Sourcing commands) and the...
Hi, In a number of projects over the last years, I have developed a set of Hibernate/EJB 3 patterns to match the DDD patterns in Part II of Evans book. Key...
I find using a ORM + RDBMS is a very painful process so whereever possible I don't do it. I either use OODBMS or just store typed events to rebuild aggregate...
I find using a ORM + RDBMS is a very painful process so wherever possible I don't do it. I don't think so. At least for me, the ORM that Django uses, isn't...
... There is in my view no confusion at all. The issue you point out seams to be one of implementation. Evans suggests implementing roles with interfaces but...
An important constraint is what the business requires you to use. In most large enterprises Oracle and/or SQL Server, and maybe MySQL exist. You end up using...
Greg, Can I safely assume that you are still using RDBMS for your reporting needs and just try to avoid using it (RDBMS) for your domain persistence? On the...
Yes SQL is great at reporting ... Db4o is a god product but there are other more mature products out there. Oodbms tend to fail because people try to report...
Ok, fundamentally it is not that different from ORM in terms of mapping event objects to relational. My word was "fits" as I am not sure it makes sense for all...
Right I agree that it's not always appropriate, there are many non- functional requirement to take into account on a per projject basis. I just wanted to make...
Greetings Eben, I spent some time reading that code a week ago. It's kinda hard for a non-Windows Forms guy to get a full understanding of it. Are you aware of...
True, and that businesses only understand RDBMS and continue to spend heavily on them. In many environments, as soon as we would recommend an OODB management...
I argue that if you look at it an fits the definition of a table perfectly so arguing against RDBMSs from that stand point is not easy to understand to say...
... If aggregate roots are not structural but rather depending on usecase, that doesn't work. You have to store each entity separately, but yes, that can be...
hey guys, I thought I knew the answer to this one! But the line is getting a little blurred at the moment in my domain model so would really appreciate your...
I would look at abstracting the decision making either into a domain entity, if it makes sense in the ubiquitous language, or a service otherwise. And further...
Does this mean that you fix only your entities and your aggregates do change (are different set of entities) per use case? ... Does this mean that you fix only...
... Since the "aggregate root" depends on the usecase and denotes consistency boundaries, yes. For example, I have Inboxes with Tasks. If I change a...
Hi Frederic, I assume you are referring to CAB. It is quite tricky --- even for a person that has used WinForms. The problem with composite UIs is that they...
Ok, but it looks like you have no aggregates at all in this case. You just have object graph and a locking schema per use case. ... Ok, but it looks like you...
Aggregate roots do not vary by use case, that is extremely inconsistent with the definition of an aggregate root and much more so consistent with the concept...
... The problem here is that Udi Dahan is re-defining the concept of an Aggregate Root. According to Udi (and Rickard) an AR is use case specific - whereas...
