The Repository Pattern explained for EVERYONE 🚀

💻 Use Code LONGERNIGHTS to get 20% off on any course or plan!

#DotNet #RepositoryPattern #PatrickGod

[cheesypufs]

Looking at this from a novice point of view I would say that you just turned a simple and concise piece of code to a more complicated one with higher maintenance requirements. You should start with mentioning the benefits, like testability, separation of concerns, scalability, reusability and encapsulation.

[hachiq]

I actually ruined my test task several weeks ago because of fat controllers. Now i know how to do it, thanks)

[CrapE_DM]

This doesn't mention a repository until the last 5 seconds.

[AthelstanEngland]

We'd call them subroutines back in the 1980s. Even different implementations could be handled by passing a parameter. Having done some work with interfaces I find them an unnecessary over engineered bloat.

[junaidkhanvibes-jkv]

I know that, but I must say your are amazing

[mamupelu]

I'm a bit slow, can you share the code?

[isahirzavalamiranda]

why dont call the class repository if we are using that pattern?

[haianh]

what if we have more and more services? some how we can add all of it?

[electrictrojan]

I learnt this the hard way, after about 10, 000 lines of botched code :(