I have a philosophical question about applying DDD to development of a rich GUI application. As a programmer I have experience in creating both DDD and DB-oriented systems so I know the basics. Now I
I\'m trying to grasp DDD here, and I\'ve read somewhere that it is possible to reuse the domain entities as viewmodels. I\'ve created a simple CRUD app, but at the U(pdate), I get a bit stuck at \"???
I am looking at a paper done by Martin Fowler called Dealing With Roles. In it, Fowler breaks out three basic strategies for dealing with roles for a Person in an organization (ie, Employee, Engineer,
In my domain, I have 2 bounded contexts that are relevant to this question: Purchasing - where the customer orders services
G\'day, I\'ve tried to do a search on a subject but couldn\'t find anything, at least yet. I have a 3 domain objects that implement interface IEntity. I\'d like to build a generic data mapper layer t
Assume you have entities, a service layer, and repositories (with an ORM like NHibernate).The UIs interact with the service layer.
I have experienced the following scenario in most web service apps I\'ve worked on: We create a Domain Model (in C#). This is the heart of the application. The Domain Model contains business and val
As a follow-up to a previous question where I asked for a solution to a broken problem, I\'m trying to find a way to express an arbitrary identifier in a \"readable\" way.
I\'m trying to get a handle on DDD and feel that I\'ve got a pretty good grasp regarding entities, aggregates, aggregate roots, repositories and value objects and how to actually represent these conce
I creating a new web site in Rails but I would like to give CoffeeScript/Node.JS a try, and the first thing I would like to do is validations, callbacks and associations on model classes in CoffeeScri
加载中,请稍侯......