Domain-driven design (DDD) is an approach to developing software for complex needs by deeply connecting the implementation to an evolving model of the core business concepts.
What is the difference between Data Access Objects (DAO) and Repository patterns? I am developing an application using Enterprise Java …
hibernate domain-driven-design ejb-3.0 repository-pattern data-access-layerI'm learning about Domain Driven Design, however there are some practical issues that are confusing to me that I think …
domain-driven-designCan somebody please explain (in succinct terms) what exactly is domain driven design? I see the term quite a lot …
domain-driven-designCan someone explain the difference between domain and application services by providing some examples? And, if a service is a …
architecture domain-driven-designI keep seeing DDD (Domain Driven Design) being used a lot in articles - I have read the Wikipedia entry …
domain-driven-designI was under the impression they are all basically the same. Are model objects also the same? Right now, in …
c# asp.net architecture domain-driven-designI'm (re)designing large-scale application, we use multi-layer architecture based on DDD. We have MVC with data layer (implementation of …
asp.net-mvc entity-framework architecture domain-driven-designI'm using NHibernate to persist my domain objects. To keep things simple I'm using an ASP.NET MVC project as …
asp.net-mvc domain-driven-design viewmodel dtoMy repositories deal with and provide persistence for a rich domain model. I do not want to expose the anemic, …
.net entity-framework domain-driven-design repository-pattern onion-architectureIn Domain Driven Design, there seems to be lots of agreement that Entities should not access Repositories directly. Did this …
oop domain-driven-design repository-pattern s#arp-architecture