Home/ Questions/Q 339343
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T10:30:51+00:00

I’m building an ASP.NET MVC app and I’m using a repository to store and

  • 0

I’m building an ASP.NET MVC app and I’m using a repository to store and retrieve view objects. My question is, is it okay for the implementation of the various repositories to call each other? I.E. can the ICustomerRepository implementation call an implementation of IAddressRepository, or should it handle its own updates to the address data source?

EDIT:

Thanks everyone, the the Customer/Address example isn’t real. The actual problem involves three aggregates which update a fourth aggregate in response to changes in their respective states. I in this case it seems a conflict between introducing dependencies vs violating the don’t repeat yourself principle.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should have a repository for each aggregate root.

    I have no knowledge of your domain-model, but it doesn’t feel natural for me to have an IAddressRepository. Unless ‘Address’ is an aggregate root in your domain.

    In fact, in most circumstances, ‘Address’ is not even an entity, but a value object. That is, in most cases the identity of an ‘Address’ is determined by its value (the value of all its properties); it does not have a separate ‘Id’ (key) field.
    So, when this is the case, the CustomerRepository should be responsible for storing the Address, as the Address is a part of the Customer aggregate-root.

    Edit (ok so your situation was just an example):

    But, if you have other situations where you would need another repository in a repository, then I think that it is better to remove that functionality out of that repository, and put it in a separate class (Service).
    I mean: I think that, if you have some functionality inside a repository A, that relies on another repository B, then this kind of functionality doesn’t belong inside repository A.
    Instead, write another class (which is called a Service in DDD), in where you implement this functionality.

    Anyway, I do not think that repositories should really call each other. If you do not want to write a Service however, and if you really want to keep that logic inside the repository itself, then pass the other repository as an argument in that specific method.

    I hope I made myself a bit clear. 😛

    • 0