I\'ve been working with S#arp Architecture but this can probably be applied to any DDD architecture (Domain / Core, Application Services, Infrastructure, and Presentation).
I have an Email object with two properties, label and value. System user need to verify their email before they can use it in the system. The verification process is very simple:
Can/Should my POCO\'s encompass multiple Databases if applicable? The reason I ask is that I am in the process of refactoring a legacy Enterprise App that was built in stages.Unfortunately, each stag
Is this a valid object design ? I have a domain object where i inject a service and call a verify method to update the state of the object and if all goes well send a confirmation message. The code lo
I have these 2 types of Users: Parents and Kids, both are Users, and have the sam开发者_如何学编程e properties, but different methods.
If you have two repositories dealing with persistance to a relational DB,开发者_运维百科 a personrepository that deals with \"Person\" objects, and an addressrepository which deals with \"Address\" ob
Abstract example: If I have a system with domains of \"Fleet\" containing a \"Vehicle\" class, and \"Customers\" containing a \"Driver\" class, where would you place a joining class (which would detai
Why aren\'t there many DDD stories that use newer nosql tools such as db4o and Cassandra for persistence.
most of the time in the service code I would have something like this: public SomeService : ISomeService
I\'m really new to DDD and trying to grasp some of the concepts. Could someone explain me the idea behind Domain Modeling in DDD.
加载中,请稍侯......