Domain-Driven Design
Updated: 8 min 16 sec ago
Thu, 09/02/2010 - 20:38
... Interesting point. Nuno, this is one of the main things I'm still confused about: Eventual Consistency. I understand the basic theory but when it comes to
Thu, 09/02/2010 - 19:28
Hi Brian, We had a discussion a while ago about this and I'd recommend you to read through it:
Thu, 09/02/2010 - 19:21
Hi Dan, You really opened my eyes! Thanks :) I'll look more into nHibernate and see how we can implement it in this scenario. But having said that, I've been
Thu, 09/02/2010 - 15:31
... Not true. If using .NET, you could implement NHibernate's NHibernate.Persister.IClassPersister interface. It'd take care of the shovelling data into and
Thu, 09/02/2010 - 12:54
Such kind of problems are better addressed by a BPM Engine than DDD. The requirement clearly asks for orchestration of two 'independent' services which
Thu, 09/02/2010 - 12:48
Hi, My understanding is that if your Aggregates and BCs are defined correctly we don't need UoW. One argument against UoW while avoiding 2PC is that it
Thu, 09/02/2010 - 11:44
You had stated you wanted to maintain consistency without relying on a UoW. I'm no DDD expert, but I and some colleagues are applying DDD principles as we
Thu, 09/02/2010 - 10:18
Hi, The question I ask is why they are both currently in separate BCs? I suspect that registrations might go over an approval process too. Dan's approach is
Thu, 09/02/2010 - 09:48
Hi Dan, Thanks for your great advice. You are right! I'm in the process of writing our own custom ORM. I know it is a pain and you may think why I am doing
Thu, 09/02/2010 - 07:26
... ok ... That's the way I see it. In contrast, Udi, I think, treats the UI as an integration point for several domains (cf mashups). That's an architecture
Thu, 09/02/2010 - 07:10
Thanks, Dan. The aggregate root in this case would actually be "Declaration", not "Car" since one can declare other goods as well and even club them with cars
Thu, 09/02/2010 - 06:14
within ... Yes. But you've described then as application services, sitting in front of the domain model. I would have them modelled as domain services,
Thu, 09/02/2010 - 06:02
... Sounds like you've just made your first steps along the path of writing your own ORM! I don't recall whether you have reasons for not using an ORM
Thu, 09/02/2010 - 05:13
After doing some research, I decided to use Reflection. I developed a clean solution to use Reflection and thought to share it here in case someone else has
Thu, 09/02/2010 - 03:54
I have a question about building a UI (in this case a web site) that deals with multiple services. A customer can declare that he is importing a car. He
Thu, 09/02/2010 - 00:48
The safe merging sections is what is used throughout the industry. As far as I know all the big players do it, including EMF, MetaEdit+, and me ;) Vaughn
Wed, 09/01/2010 - 21:45
C# is not my territory so probably I won't be of much help there. Abstract classes and interface delegation approach work well if you are generating for a
Wed, 09/01/2010 - 20:24
Greg, Any word on these courses being available as videos in the future? I would love to see it but have not been able to make it work with my schedule, an
Wed, 09/01/2010 - 19:23
Brian, Can you elaborate more on this? I'm not sure how you're going to solve this problem with UoW and a domain service. Cheers, Mosh
Wed, 09/01/2010 - 17:43
Hi Rafael, I will probably support FC at some point. Well, you have the full MDD mindset. We different in opinion about generated code because I believe that