Design Patterns - Repository

design-patterns

https://www.youtube.com/watch?v=kMbgH2qRxqQ
http://www.lestard.eu/2015/generic_repository_part1/
http://blog.lowendahl.net/data-access/the-repository-pattern-explained-and-implemented/
http://hannesdorfmann.com/android/evolution-of-the-repository-pattern
http://panavtec.me/what-is-the-repository-pattern-and-why-im-not-going-to-use-it-on-android
https://code.tutsplus.com/tutorials/the-repository-design-pattern--net-35804
http://stackoverflow.com/questions/31305199/repository-pattern-how-to-understand-it-and-how-does-it-work-with-complex-en
https://thinkinginobjects.com/2012/08/26/dont-use-dao-use-repository/
https://medium.com/@krzychukosobudzki/repository-design-pattern-bc490b256006#.m63gpix4y

What is the purpose of the Repository pattern?

The repository pattern is very useful for implementing search methods and mini-query languages. It takes these queries and uses a gateway to obtain the data for a factory to produce the objects you need.

You need the repository pattern when you need to create multiple objects based on search criteria, or when you need to save multiple objects to the persistence layer.

The purpose is to let clients that need specific objects to work with a common and well isolated query and persistence language. It removes even more creation-related code from the business logic.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License