domain-driven-design

domain-driven-design

Repository or ServiceAgent in DDD

Value object or entity

Value Objects in CQRS - where to use

DDD How to fetch a list of value objects

Where is the proper place to put domain logic to update a child of an aggregate root?

How to define aggregate roots from a relational model in order to use it for DDD?

What is the Aggregate root in this case

What is the recommended way to add child entities to aggregate roots?

Aggregate root design and presentation layer

How to Correctly Model this Polymorphic Association?

Best Place To Save Domain To Write Database In CQRS (Command Handler or Domain Event Handler)

Please clarify how create/update happens against child entities of an aggregate root

stackoverflow tag problem Vo or entity or seperate root agg

save,progress,DDD,Entity

accessing app service from domain object

domain service calling from domain entity

Does DDD allow for a List to be an Aggregate Root?

Recommended way to create aggregate entities

Unit of work in Nhibernate

Domain object referenced by two Aggregate roots

CRUD in domain driven design

Many to many relationship in ddd

Specification Pattern in a separate Project?

Accessing interfaceof model service in model entity

many to many relationship in ddd

Root aggregate problem in domain driven design

saving list of value objects in table

DDD - Bounded Contexts and Multiple Models?

One domain object 'filled' by several repositories

Root aggregate reference problem

Interface with service layer or domain objects themselves? (DDD)

Persistence encapsulated via the domain, or persistence via the Repository?

Do I must expose the aggregate children as public properties to implement the Persistence ignorance?

DDD - How Can I Avoid Crossing Aggregate Boundaries Here?

DDD - aggregate roots in a very simple blog model

Handling External Dependencies in a Factory

What's the intent of the Rollback method in the Unit of Work pattern?

What result does a Command request return in CQRS design?

domain objects and repository

Is using DAO in domain objects correct?

Persist/store in domain or application layer?

Domain Driven Design: Should Repository methods be passed a configuration string?

Qualifier concept in ddd

Can a single entity be a non-aggregate?

What's an Exclusivity Arc called in UML

Working with Aggregates in DDD

Which layer should scheduled task be put?

DDD vs N-Tier (3-Tier) Architecture

Is it correct to let entities call repository store methods?

Domain-driven-design (DDD) pitfalls

In domain driven design, can entities have their own repositories?

How do you deal with DDD and EF4

Domain Driven Design Aggregates

Domain Modeling, Domain Objects in DDD

DDD modeling, interaction between aggregate roots

What is the Future of Domain/Entity programming at Microsoft?

Which layer should Repositories go in?

Can the domain model and repositories be in seperate dlls?

Domain Driven Design - Interfaces for defining roles

Any good book on domain driven design? [closed]

page:21 of 23 prev page next page main page

Categories

database-administration

shared-libraries

switch-statement

general-network-error

google-cloud-monitoring

file-get-contents

javaapplicationstub

sql-query-store

wechat-miniprogram

google-content-api

multiplechoicefield

ruby-on-rails-4.2

hierarchyviewer

installshield-2010

blackberry-eclipse-plugin

self-organizing-maps

windows-live-writer

Resources