Quick question... When approaching something like an email address the immediate idea is to treat this as a value object.
As you may have seen the question from the title, i\'m little bit confused about where to put the ViewModel classes in our web project. What is the 开发者_StackOverflow中文版best practice to putting V
I have an entity structure as follows: IManager: IDeletable { IEnumerable<IFund> Funds {get;} IFailureNotification Delete();
How should separate aggregate roots (AR) communicate with one another in an environment built on DDD principles using an event-sourced aggregate back-end?
I had asked this question in a much more long-winded way a few days ago, and the fact that I got no answers isn\'t surprising considering the length, so I figured I\'d get more to the point.
I\'m currently determining the entities, value objects and aggregates in a system. Say the following Entities have been identified:
Is is good practice to use domain objects as keys for maps (or \"get\" methods), or is it better to just use the id of the domain object?
Pardon the length here...hopefully I didn\'t go overboard... I\'m in the process of working on my first production MVC application and I\'m trying to stick to DDD principles in the process.I\'ve run
I\'m reading through Eric Evans\' awesome work, Domain-Driven Design. However, I can\'t help feeling that the \'layers\' model is contrived. To expand on that statement, it seems as if it tries to sho
I have been trying to understand DDD for few weeks now. It开发者_如何学编程s very confusing. I don\'t understand how I organize my projects. I have lot of questions on UnitOfWork, Repository, Associat
加载中,请稍侯......