I\'m learning DDD and wanted to start modelling a fairly trivial example, a blog application. One area开发者_StackOverflow中文版 I\'m a little confused about is defining aggregate roots.
Is it ok for a Repository to return boolean values based on objects it (virtually) c开发者_Python百科ontains?
I\'m refactoring a project using DDD, but am concerned about not making too many Entities their own Aggregate Root.
Ive been struggling with this for like some time. If you do an architecture like 开发者_Go百科this..
I\'ve asked a previous question last month, about whether an Entity should access a Repository, and although it looks like most people think they shouldn\'t, I have to admit it\'s hard for me to get c
I am writing a Java DDD application in which the database model is already designed and implemented. The problem i开发者_开发问答s that my domain objects differs from the database model and the the OR
After reading several other questions, it looks like it\'s not advisable to have an entity class use a Repository. So given these repositories:
Say I\'ve got two simple entities: User and Review. How bad is it if User calls the Review repository? What is the \"clean\" way for the User to get its Reviews?
In a nutshell, my domain allows users to submit stories (about a person or team of people) that contain a multitude of different states and transitions its can be in and what behavior is allowed durin
During the life of my web application I know all of my services and repositories will be called. I would like to instantiate them once during the startup of the web application and refer to the instan
加载中,请稍侯......