I have Person aggregate in which Address is part and vo , but now i have another aggregate Payment which have another VOPaymentInfo , which contains details like Creditacard number and other details,
I would like some advice and critique with the domain driven design below.I\'ve included pseudocode below. The real code would have encapsulated properties.
and thanks in advance for your time. We are using CSLA 3.5.1, although, ultimately, this problem may not have much to do with CSLA.
My Vehicle type: public class Vehicle : EntityObject { private Lazy<string> _nameFromDelegate = null;
I\'m working on migrating an application to NHibernate, and I\'m using Fluent NHibernate. I\'m running into an issue mapping a collection of value types to an aggregate root.
I have just been re-reading \"Domain-Driven Design: Tackling Complexity in the Heart of Software\" by Eric Evans. I could not help but notice a hint towards creating a language where there is a one-to
I\'m new to domain driven design and would like to hear your thoughts on a design decision: In my domain, I have the entities \"voyage\" and \"booking\".
I have Person class which is root of its aggregate, this aggregate also contains country and state province as vo.
How do you layout your Maven modules when doing DDD projects? Do you fit all layers (presentation, application, domain, infrastructure) in a single module, or do you create a multi-module layout with
In my last question I posted some sample code on how I was trying to achieve separation of concerns.I received some ok advice, but I still just don\'t \"get it\" and can\'t figure out how to design my
加载中,请稍侯......