I am building an application that tries to abide by clean architecture. I understand that the repository is meant to abstract away the persistence layer and return back entities in terms of the dom...

NOTE I'm not asking if I should use the Repository pattern, I care about the How. Injecting persistence-related objects into domain classes is not an option for me: it makes Unit Testing impossible...

In a DDD-project I'm contributing to, we're seeking for some convenient solutions to map entity objects to domain objects and visa versa. Developers of this project agreed to fully decouple domain...

I have the following DDD scenario, grouped into the following aggregates: User, Friends (User Associations), File (for user uploading), Galleries (grouping of files), Messages (user communication)...

I'm struggling with a basic issue. The project is in C#, but the issue is general. I'm following the always valid object principle. As one example I have a product entity that has a mandatory prope...

What would be a rule of thumb when designing an aggregate in DDD? According to Martin Fowler, aggregate is a cluster of domain objects that can be treated as a single unit. An aggregate will have ...

Which layer should the repository classes go in? Domain or Infrastructure?

I have a domain model Customer - Aggregate root - because an order can't exist without a customer Order - entity OrderStatus - value object In my form I need a list of all OrderStatuses. Sho...

As I understand, there is a 1-1 relation between a Repository and a AggregationRoot. Suppose I have an AggregationRoot_A with an attribute holding an id for an AggregationRoot_B. I will have Reposi...

I'm trying to get my head around how to properly use the repository pattern. The central concept of an Aggregate Root keeps coming up. When searching both the web and Stack Overflow for help with w...

Building a time tracking application I am trying to determine the best way to design the aggregate roots. The basic core entities are Client, Project, Employee, ProjectAssignment, Department, Time...

After reading lot of posts, I realised if an aggregate root exists for a concept/context, we need to have a single repository for that whole concept/context. If thats the case, I see there won't b...

I am confused about Domain Driven Design Approaches. From the sources on net I understood it is way of segregating your Domain Objects and Database Objects but I don't understand the difference bet...

One common reaction that I see for a lot of questions asked here and other forums are like "You don't need to do DDD for that. Its a simple CRUD application, DDD is an over-engineering". Well I a...

Is it generally acceptable that one repository can access another repository? Specifically in this case, I have one aggregate root that uses another aggregate root to determine what entities to add...

DDD recommends that the domain objects should be in a valid state at any time. Aggregate roots are responsible for guaranteeing the invariants and Factories for assembling objects with all the requ...

Why are repositories' .Add method usually implemented as accepting the instance of entity to add, with the .Id already "set" (although it can be set again via reflection), which should be...

I'm currently designing a backend for a social networking-related application in REST. I'm very intrigued by the DDD principle. Now let's assume I have a User object who has a Collection of Friends...

I want to create an app by implementing DDD using Spring. Let's say I have a business entity Customer and an interface CustomerRepository. Since spring provides CrudRepository and JpaRepository to...

I am in the process of refactoring an application and am trying to figure out where certain logic should fit. For example, during the registration process I have to check if a user exists based upo...

I am working on an existing application the uses the Generic Repo pattern and EF6 database first. I am calling a stored proc that returns a complex type that is not an existing entity in my entity ...

I've read and came to realize myself that entities (data objects - for JPA or serialization) with injections in them is a bad idea. Here is my current design (all appropriate fields have getters an...

A current project needs us to persist domain objects in a NoSQL database such as mongoDB. In many examples (incl. Eric Evans, Vaughn Vernon) the domain objects are serialized and persisted to the m...

If we consider a standard persistence repository, the solution is easy. We put the IStuffRepository in the Domain Layer, and the StuffRepositoryImplementation in the Infrastructure Layer. But what...

I have a question. we are using a generic repository and our domain model is also the persistence model but that caused us to tweak our Domain Model a lots to be a aligned with the ORM, for example...