I understand the basic principle but I have trouble determining what is the hard line separating responsibilities of a Repository or a Service. I’m mostly thinking in terms of c# .NET in the following example but I think the design pattern is kinda universal.

Let’s say I have tables “Movie” and “Genre”. A movie might have multiple genres associated with it. I have a MovieController with the usual CRUD operations. The controller talks to a MovieService and calls the CreateMovie method for example.

The MovieService should do the basic business checks like verifying that the movie doesn’t already exist in the database before creating, if all the mandatory fields are properly filled in and create it with the given Genres associated to it. The Repository should provide access to the database to the service.

It all sounds simple so far, but I am not sure about the following:

  • which layer should be responsible for column filtering? if my Dto return object only returns 3 out of 10 Movie fields, should the mapping into the return Dto be done on the repository or service layer?

  • if I need to create a new Genre entity while creating a new movie, and I want it to all happen in a single transaction, how do I do that if I have to go through MovieRepository and GenreRepository instead of doing it in the MovieService in which i don’t have direct access to the dbcontext (and therefore can’t make a transaction)?

  • let’s say I want to filter entries specifically to the currently logged in user (every user makes his own movie and genre lists) - should I filter by user ID in the MovieService or should I implement this condition in the repository itself?

  • is the EF DbContext a repository already and maybe i shouldn’t make wrappers around it in the first place?

Any help is appreciated. I know I can get it working one way or another but I’d like to improve my understanding of modern coding practices and use these patterns properly and efficiently rather than feeling like I’m just creating arbitrary abstraction layers for no purpose.

Alternatively if you can point me to a good open source projects that’s easy to read and has examples of a complex app with these layers that are well organized, I can take a look at it too.

  • walter_wiggles@lemmy.nz
    4·
    3 months ago

    I’m not too familiar with EF specifically, but I’ll give you my general advice:

    1. Column filtering can be done in either the repository or service layer.
    2. Your transaction should be scoped to the service method. MovieService should call both repositories.
    3. Prefer filtering in the repository
    4. I don’t know this one
    • Cyno@programming.devOP
      1·
      3 months ago
      1. but if I do it on the repository layer I have to have a separate method for every possible filter combination, right? if i want to do it on the service layer i have to return an IQueryable which is also allegedly a bad practice (and i might as well return the entire dbset at that point)? also, should the repository be aware of my application (or even view) layer dto models?
      2. this means the service has direct access to the database (dbcontext in this case)? or do you expose opening a transaction through some repository too?
      • walter_wiggles@lemmy.nz
        2·
        3 months ago
        1. See GetOffMyLan’s comment. An application will have a finite set of queries it needs to make. Depending on the complexity you may have to enumerate them, but sometimes you can build them up dynamically, or even come up with SQL that will cover multiple cases depending on parameter values.
        2. I think GetOffMyLan’s advice applies here too.

        When you’re creating a layered architecture you want to limit a lower layer from knowing what’s above it. If you tightly couple your data layer to the view then you lose flexibility. Imagine having to implement some batch processing features that don’t involve the web.

        A lot of this is overkill for a small app so if some it seems pointless it may be because there isn’t a team of devs working on the same codebase.