The first 25 seconds of this tutorial alone, does a better job explaining the repository pattern than a hundred other tutorials on CZcams. This is the best tutorial on repository pattern.
This is not simply an explanation on the repository pattern. This video reaches about so many principles that young engineers have a hard time acquiring. I already knew all of those concepts but never truly acquired them. You shine bright so strong on those concepts that I now not only understand them, but I also have intuition and instinct about looking out for improvements like those to decouple and reuse code. There is no code per se, yet it did serve as a wonderful example.
The only problem with this channel is that it has only two videos. Please, post more! High-quality content, easily digestible explanations, and top-notch edition. You got one more subscriber.
Why do you only have 2K subscribers?! This is the only one of at least 10 previous videos that has explained Repositories for a true beginner to understand! And this video is 3 years old. Thank you for this!
In DDD your repositories should be per aggregate rather than business object. An aggregate may be a business object but it may be more than just one, depending on your needs to enforce consistency during a write. This usually works well with the repository as you'll open a transaction as part of the repository operation.
How does this guy don't have a million subs? Explains very well and is easy to understand, only thing I'd suggest is giving quick demo example in the video. Keep up the good work!
This is such high-quality content, man! Superb production. You deserve tons of more subscribers. Maybe pushing more videos every week will do the trick.
In the Generic Implementation section, I think you wanted the IRepository to have a Find method of T entity Find(long id) because it will return the T type for any implementation and not just User
You are right! Thank you for pointing that out! That was an oversight on my part. I’ll see if I can add a note at that part of the video to clarify things. Thanks again for letting me know!
Appreciate the nice comment. I am working on another video. Just takes me some time because it’s something I do in my spare time and I’ve been busy at work. I plan on going through the DDD concepts first and take it from there.
The Repository pattern seems simple. Great! I need to implement it in my project! I'm making it. Fabulous! Wait... I need filters... Damn. What I should do? Should I add filtering methods to the repository? It is a bad idea. I need to read the Internet. Hmm... CQRS? Now I have to use the Repository only to update the business object. To get composite data I have to use Queries. They are not so clean anymore. They usually know about the database type. What's the result? The simple idea of a Repository results in a complex mess of Repositories and Queries. Usually there is also a Unit of Work running nearby. What do you think about compound queries in the context of the Repository?
For most cases it’s usually acceptable to have different method definitions. -FindByName -FindByEmail -FindByPhone etc.. If your query is particularly complex, or it needs to be used in other areas of the system, typically complex business logic, you may want to look into the specification pattern. In short, you would encapsulate the query logic inside the specification object, and then inject that specification wherever needed, in this case, a repository. Happy Coding! Rob
Interesting question! I haven't thought about it from this context. There isn't an obvious tradeoff or drawback that comes to mind. I would say the biggest debate I've seen regarding the pattern has delt with specific implementations. Particularly when injecting an Object Relational Mapper (ORM) such as Entity Framework, which already implements the Repository Pattern (with unit of work) itself and will lead to code duplication and violation of the DRY principle (Don't Repeat Yourself).
@@CodingConcepts Why would you inject an ORM if you already created a custom data access layer with the repository pattern? The only reason I see where you would reach such a situation is if your main data access is already an ORM and you also integrate your own repository for more custom work. Wouldn't this scenario only create complementary code, thus not violating the DRY principle? (i mean it's still not 100% DRY, but still reasonably well)
@@pictzone Great question! There is no definitive answer to this and it really comes down to the trade-offs you're willing to accept. I find myself writing my own repository classes because I find it makes my code much more testable. I'm a strong advocate for Test Driven Development (TDD) and I believe good code is testable code. By writing my own repositories, I'm able to easily mock their return values with testing tools such as Moq. I'm able to reduce the duplicate code it creates, which you've correctly identified, by using generic repositories in a lot of cases. ORM tools do provide in memory testing tools, but I just don't find the usability as streamlined as Moq. So for me, I find the trade off of increased testability at the cost of some duplication acceptable.
Great explanation. Just one suggestion, please do not use Uppercase everytime. It is sometimes very hard to read the content displayed over the screen.
Of course! At 2:24 I was trying to illustrate a scenario where a lot of logic resides in the controller. When you see "thick" or "bulky" controllers like this, it becomes very difficult to test your code because of the dependencies these controllers are using. ie: a database. The design at 2:45 is improved because it moves the database dependency out of the controller and into the repository. This puts us in a position to use a Mock for our repository to better target the specifc area of code we're looking to test. Hope this answers your question. Happy Coding! Rob
In case the data comes from another application, like from another REST API. Can the implementation of the Repository, be the consumer client of the REST API? Or Repository Pattern only applies to something like Databases?
You’re typically going to be using the repository pattern in conjunction with a database or some other data store. You could receive data from a REST Api such as a CustomerId to then fetch additional information about that customer using a repository. I hope that clears things up for you.
What can be done for other complex operation how to segregate those in terms of repositories? outrside crud we might need more methods in a large software
Are you sure about generic interface repo? Not all repositories should look like this. Some business objects should not be deleted, other should not be updated.
I agree. Not trying to make the argument that a generic repository is best in all cases. Just trying to show different strategies and implementations. Appreciate your comment.
There is a pretty good discussion I had in the comments about this with another viewer. I linked the comment below. Let me know if that clears things up. czcams.com/video/x6C20zhZHw8/video.html&lc=UgwoV2MDbSnxx_sXtFR4AaABAg
@@titobundy Sorry about that. I'm not seeing the comment any more. I will post the discussion here. Question: I might be confused but i find this pattern really similar to the use of Data Access Objects. Are there any differences ? Should we be using one over the other ? Reply: A Data Access Object (DAO) is all about data persistence. It will sit below the Repository, and will match one to one with an underlying database table or view. It's an object representation of the underlying data schema. It's logicless. The return type of a repository is going to be an Entity or Aggregate which are business objects. They may closely resemble the underlying data schema, but you're getting business objects back. Which will have some form of business logic in them. In general, you'll see DAOs used in more complex architectures, to handle specific persistence requirements. Question: So if i understood correctly, they are used together and DAO will return data as JSON for example, when Repository will cast it to Business objects (and perform other operations) ? Do you have some tips on how to know if we should use DAO, repository or both ? Reply: A repository is an abstraction of a collection of objects. A DAO is an abstraction of data persistence. A UserRepository should only ever return User. It shouldn't for example return a RoleObject. A UserDAO on the other hand, it would be acceptable to return information about a User and have another method to return information about it's Roles. As it's only concern is how the information is persisted/stored in the database. The key thing to note here is it's just returning data for you. A good use case for a DAO would be when the underlying data schema is very complex. Perhaps, that UserObject needs several database operations behind the scenes to construct. Put logic like that in a DAO, not a Repository. An Object Relational Mapper (ORM) such as Entity Framework, is going to eliminate the need for a DAO in most cases. It's going to do most of that work for you.
@@CodingConcepts Thank for your post. I would like to have your point of view. Do you think tools like TypeOrm or Spring Data, which apply the repository pattern, do so according to Martin Fowler's definition in his book Refactoring or perhaps Eric Evans in his book DDD, or do you think such implementations are closer to what DAO offers?
@@titobundy I can't speak specifically to TypeOrm or SpringData as I haven't used those tools before, I mainly use Entity Framework. But in general, I would say both. Modern ORM's are applying the repository "by the book" but are also becoming exceptionally well at mapping complex data objects. I would expect the need for a DAO layer to decrease over time.
I wish I had more time to pick this up so I know how to communicate with my devs and explain how I need to be able to access payment history and user referrals with my flutter app so I can create reports to keep my affiliates and stockholders up to date… if any one has any tips please share. I appreciate you so much in advance.
![Laravel урок №25: [ Что такое Репозиторий? #1 ]](http://i.ytimg.com/vi/Y-GxEsNiIGU/mqdefault.jpg)
The first 25 seconds of this tutorial alone, does a better job explaining the repository pattern than a hundred other tutorials on CZcams. This is the best tutorial on repository pattern.
Thank you very much. I really appreciate it.
Seriously though!
He get’s straight to the point!
This is not simply an explanation on the repository pattern. This video reaches about so many principles that young engineers have a hard time acquiring.
I already knew all of those concepts but never truly acquired them. You shine bright so strong on those concepts that I now not only understand them, but I also have intuition and instinct about looking out for improvements like those to decouple and reuse code.
There is no code per se, yet it did serve as a wonderful example.
The only problem with this channel is that it has only two videos. Please, post more! High-quality content, easily digestible explanations, and top-notch edition.
You got one more subscriber.
Thank you! I’m working on getting another one out.
this is the only video where I was able to understand Repository Pattern. Short but the way the lesson is delivered is clear and easy to digest.
Thank you! I had the gut feeling this vid would give me the answers I was looking for. Should have watched it first and saved time!
One of the best explanations of design patterns I have ever seen. Keep up the great work
Why do you only have 2K subscribers?! This is the only one of at least 10 previous videos that has explained Repositories for a true beginner to understand! And this video is 3 years old. Thank you for this!
Thank you!
In DDD your repositories should be per aggregate rather than business object. An aggregate may be a business object but it may be more than just one, depending on your needs to enforce consistency during a write. This usually works well with the repository as you'll open a transaction as part of the repository operation.
Absolutely amazing video, as a relatively inexperienced developer I’m currently learning C# and this video has made complete sense to me.
How does this guy don't have a million subs? Explains very well and is easy to understand, only thing I'd suggest is giving quick demo example in the video. Keep up the good work!
He put up two videos and ghosted.
@@ewomer100 A year ago he seemed very promising ngl
Man, that is the bet explication about that design pattern that I've seen. Thank you so much for your effort
This was the best explanation of the Repository Pattern. Thank you for this.
Hoping that you make some more videos on design patterns. Thank you. Keep up the good work!
Best tutorial ever! So much explained in so little! ❤️
I don't comment often on videos, but this video definitely deserves a THANK YOU!!
Keep them coming. People will love your tutorials!
Great explanation on the Repository pattern. It makes so much sense to me now.
This is such high-quality content, man! Superb production. You deserve tons of more subscribers. Maybe pushing more videos every week will do the trick.
I just found this video and your channel. Please continue your amazing work again and keep creating these kind of content 💪🏻
Awesome video! Very clean and clear and explanation is spot on.
This is the best video about this topic I have found on CZcams!
Thank you!
Hey man, thanks so much for this. Me, Dom and Max love your work.
Very well explained. Life saver literally. Thank you
Best video i ever heard about the Repository pattern
In the Generic Implementation section, I think you wanted the IRepository to have a Find method of T entity Find(long id) because it will return the T type for any implementation and not just User
You are right! Thank you for pointing that out! That was an oversight on my part.
I’ll see if I can add a note at that part of the video to clarify things.
Thanks again for letting me know!
really good video with good diagrams. Expecting more videos from you.
Loved the topic and the explanation.
This is such a great video. I'm so glad I found your channel. Are you planning on creating more videos like this?
Great videos. Subscribed. Would like to see more industry real life examples. Especially this part ( 10:46 ).
Wow, this is amazing work. Thank you!
Amazing video
Thanks a lot for these explanations, illustrations nice as well
Crystal Clear Explanation.
Great video.I hope you can make some more.
Man, this is very good video
Thank you 😊
We will waiting for your videos
Great Job Buddy ......
Great video boss👍💥👌
awesome content, more about design pattern please.
the best explanation ever 🙌🙌🙌
nice and easy to understand straight to the point thx a lot
Great explanation , thank you :)
just the video I needed, thanks c:
Great video!
Amazing video, thank you.
You are cool, make more videos like this, and your channel will grow very quickly!
this is high quality concepts, too bad this channel ended up only with 2 videos. i still waiting for another concepts. keep up the good work.
Thanks! I’m working on another video. Apologize for the delay!
@@CodingConcepts :D
@@Zoreens I’m working on one. Promise 🙂
Hey, are you planning to continue on design patterns (and other topics) in this channel? Really nice explanations!
Appreciate the nice comment.
I am working on another video. Just takes me some time because it’s something I do in my spare time and I’ve been busy at work.
I plan on going through the DDD concepts first and take it from there.
The best!
Thanks
Thanks man! Please post more
Thank you!
The Repository pattern seems simple. Great! I need to implement it in my project! I'm making it. Fabulous! Wait... I need filters... Damn. What I should do? Should I add filtering methods to the repository? It is a bad idea. I need to read the Internet. Hmm... CQRS? Now I have to use the Repository only to update the business object. To get composite data I have to use Queries. They are not so clean anymore. They usually know about the database type. What's the result? The simple idea of a Repository results in a complex mess of Repositories and Queries. Usually there is also a Unit of Work running nearby. What do you think about compound queries in the context of the Repository?
For most cases it’s usually acceptable to have different method definitions.
-FindByName
-FindByEmail
-FindByPhone
etc..
If your query is particularly complex, or it needs to be used in other areas of the system, typically complex business logic, you may want to look into the specification pattern.
In short, you would encapsulate the query logic inside the specification object, and then inject that specification wherever needed, in this case, a repository.
Happy Coding!
Rob
thanks very much!
wow, thank you very much !
Thank you so much!
You’re welcome!
Wow , just wow 👏👏
Great!!!
great job
That's really great
Cool
keep it up!
eagerly waiting new video.
nice one!
impressingly precise and consice. Haven't seen this explained that clear before. Do the pattern have any drawbacks? Keep up the good work!
Interesting question! I haven't thought about it from this context.
There isn't an obvious tradeoff or drawback that comes to mind. I would say the biggest debate I've seen regarding the pattern has delt with specific implementations.
Particularly when injecting an Object Relational Mapper (ORM) such as Entity Framework, which already implements the Repository Pattern (with unit of work) itself and will lead to code duplication and violation of the DRY principle (Don't Repeat Yourself).
@@CodingConcepts Why would you inject an ORM if you already created a custom data access layer with the repository pattern? The only reason I see where you would reach such a situation is if your main data access is already an ORM and you also integrate your own repository for more custom work. Wouldn't this scenario only create complementary code, thus not violating the DRY principle? (i mean it's still not 100% DRY, but still reasonably well)
@@pictzone Great question!
There is no definitive answer to this and it really comes down to the trade-offs you're willing to accept.
I find myself writing my own repository classes because I find it makes my code much more testable. I'm a strong advocate for Test Driven Development (TDD) and I believe good code is testable code.
By writing my own repositories, I'm able to easily mock their return values with testing tools such as Moq.
I'm able to reduce the duplicate code it creates, which you've correctly identified, by using generic repositories in a lot of cases.
ORM tools do provide in memory testing tools, but I just don't find the usability as streamlined as Moq.
So for me, I find the trade off of increased testability at the cost of some duplication acceptable.
I sub
Great explanation. Just one suggestion, please do not use Uppercase everytime. It is sometimes very hard to read the content displayed over the screen.
Thanks for the feedback!
Could you please elaborate more about the test problem at 02:24 till 02:45? I don't understand how this makes it harder to write a test
Of course!
At 2:24 I was trying to illustrate a scenario where a lot of logic resides in the controller. When you see "thick" or "bulky" controllers like this, it becomes very difficult to test your code because of the dependencies these controllers are using. ie: a database.
The design at 2:45 is improved because it moves the database dependency out of the controller and into the repository. This puts us in a position to use a Mock for our repository to better target the specifc area of code we're looking to test.
Hope this answers your question. Happy Coding!
Rob
👍
In case the data comes from another application, like from another REST API.
Can the implementation of the Repository, be the consumer client of the REST API?
Or Repository Pattern only applies to something like Databases?
You’re typically going to be using the repository pattern in conjunction with a database or some other data store.
You could receive data from a REST Api such as a CustomerId to then fetch additional information about that customer using a repository.
I hope that clears things up for you.
Very helpful! Flexibility is spelled wrong throughout haha.
Thank you for letting me know!
thanks man
You’re welcome!
@@CodingConcepts woah you still active on CZcams ? Nice
Yup 🙂
What about aggregation root?
What can be done for other complex operation how to segregate those in terms of repositories? outrside crud we might need more methods in a large software
Take a look at the specification pattern
GOLD
Post more videos
come back bro
Are you sure about generic interface repo? Not all repositories should look like this. Some business objects should not be deleted, other should not be updated.
I agree. Not trying to make the argument that a generic repository is best in all cases. Just trying to show different strategies and implementations. Appreciate your comment.
what is the difference between the DAO and the Repository pattern?
There is a pretty good discussion I had in the comments about this with another viewer. I linked the comment below. Let me know if that clears things up.
czcams.com/video/x6C20zhZHw8/video.html&lc=UgwoV2MDbSnxx_sXtFR4AaABAg
@@CodingConcepts I don't see the discussion. Is the url correct?
@@titobundy Sorry about that. I'm not seeing the comment any more. I will post the discussion here.
Question: I might be confused but i find this pattern really similar to the use of Data Access Objects. Are there any differences ? Should we be using one over the other ?
Reply: A Data Access Object (DAO) is all about data persistence. It will sit below the Repository, and will match one to one with an underlying database table or view. It's an object representation of the underlying data schema. It's logicless.
The return type of a repository is going to be an Entity or Aggregate which are business objects. They may closely resemble the underlying data schema, but you're getting business objects back. Which will have some form of business logic in them.
In general, you'll see DAOs used in more complex architectures, to handle specific persistence requirements.
Question: So if i understood correctly, they are used together and DAO will return data as JSON for example, when Repository will cast it to Business objects (and perform other operations) ?
Do you have some tips on how to know if we should use DAO, repository or both ?
Reply: A repository is an abstraction of a collection of objects.
A DAO is an abstraction of data persistence.
A UserRepository should only ever return User. It shouldn't for example return a RoleObject.
A UserDAO on the other hand, it would be acceptable to return information about a User and have another method to return information about it's Roles. As it's only concern is how the information is persisted/stored in the database. The key thing to note here is it's just returning data for you.
A good use case for a DAO would be when the underlying data schema is very complex. Perhaps, that UserObject needs several database operations behind the scenes to construct. Put logic like that in a DAO, not a Repository.
An Object Relational Mapper (ORM) such as Entity Framework, is going to eliminate the need for a DAO in most cases. It's going to do most of that work for you.
@@CodingConcepts Thank for your post. I would like to have your point of view. Do you think tools like TypeOrm or Spring Data, which apply the repository pattern, do so according to Martin Fowler's definition in his book Refactoring or perhaps Eric Evans in his book DDD, or do you think such implementations are closer to what DAO offers?
@@titobundy I can't speak specifically to TypeOrm or SpringData as I haven't used those tools before, I mainly use Entity Framework.
But in general, I would say both. Modern ORM's are applying the repository "by the book" but are also becoming exceptionally well at mapping complex data objects.
I would expect the need for a DAO layer to decrease over time.
I wish I had more time to pick this up so I know how to communicate with my devs and explain how I need to be able to access payment history and user referrals with my flutter app so I can create reports to keep my affiliates and stockholders up to date… if any one has any tips please share. I appreciate you so much in advance.