I want to enforce some rules every time a domain object is saved but i don\'t know the best way to achieve this. As, i see it, i have two options: add a save method to the domain object, or handle the
I\'m refactoring a project using DDD, but am concerned about not making too many Entities their own Aggregate Root.
I need just a few confirmation that I do some stuff in the right way or I make horrible mistake :) 1) I put my data access layer (MyProject.Domain) in sepparate assembly. There I have entity object \"
I\'m fairly new to DDD and have read a few articles about the concept so pardon if I\'m lacking some knowledge. I\'m curious on how this example should be modeled with aggregate roots.
I\'d like to model an Address as a value object. As it is a good practice to make it immutable, I chose not to provide any setter, that might allow to modify it later.
Look at my Controller (I\'m using Dependency Injection to manager dependencies): public RoleController(IRoleRepository roleRepository, ISiteRepository siteRepository, IUserRepository userRepository,
Excuse me for my poor English. Ok, I\'m thinking about DDD approach now and it sounds great but... There is one little question about it. DDD says that the domain model layer is totally decoupled fro
I have a question how to deal with a saga where the decision making depends on an event that was published before the saga was created.
I\'m looking for a way to return an immutable collection from a domain object in Doctrine 2. Let\'s start with this example from the doc:
I am stuck in a vortex of analysis paralysis trying to apply DDD to various applications i have either developed in the past or plan on doing in the future.
加载中,请稍侯......