ddd-repositories

The repository pattern suggest that you can only pull aggregate roots. But how would you retrieve a single child using only it's uniqiue identity(Child.ID) if you do not know it's parent(root)? class Parent { public int ID { get; set; } IEnumerable<Child> Children { get; private set; } } class Child { public int ID { get; private set; } public virtual Parent Parent { get; private set; } // Navigational model } My application is stateless (web), for simplicity, the request only contains the ID of the child. I am thinking three approaches: Call all the parents then ask them politely who owns

Aggregates must be designed to be transactionally and eventually consistency. This consistency boundary around entities helps manage complexity. In our repository implementations, we are using Entity Framework to interface with the actual database. Historically we have always had huge contexts (spanning scores of tables) which represent every available table, field and relationship in the database (or at least in some functional area of the database). The problem here is that this context is used for hundreds of different things and grows exponentially as the system gets bigger, leading to

In my application a few layers. In this topic will focus on Domain and Infrastructure layers. I have repository interface ClientRepositoryInterface in Domain layer. And I have implementation of this interface ClientRepositoryImpl in Infrastructure layer. But to reconstitute the object in the middle of the cycle of its existence I need factory(ReconstitutionClientFactory). Call the factory will be in the repository. The book by Eric Evans is described as a normal practice. But where this factory(ReconstitutionClientFactory) should be located? In Domain or in Infrastructure layer? I think in

I have a question regarding DDD and the repository pattern. Say I have a Customer repository for the Customer aggregate root. The Get & Find methods return the fully populated aggregate, which includes objects like Address, etc. All good. But when the user is searching for a customer in the UI, I just require a 'summary' of the aggregate - just a flat object with summarised information. One way I could deal with this is to call the find method on the repository as normal, and then in the application layer, map each customer aggregate to a CustomerSearchResult / CustomerInfo DTO, and send them

I need to clarify something. Have Person Aggreagate , 2 VOs (Country, StateProvince). I want to load all country in my presentation layer (i am using mvc) Evan says you only use repository (IPersonRepository) to work with root entity (it should always return just a reference to the Aggregate Root) public interface IPersonRepository() { void savePerson(Person p); void removePerson(Person p); Ilist<Person> getPerson(); } what i usually do to solve this : Add in IPersonRepository this method IList<Country> LookupCountrysOfPerson(); In Infra layer implement the Domain interfaces like this: public