gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

#55 Added Repository description to README.md

Browse Source
This commit is contained in:
Ilkka Seppala 2015-07-22 01:15:30 +03:00
parent a290c1af13
commit 9040c8bec6
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@ -88,6 +88,7 @@ An architectural pattern is a general, reusable solution to a commonly occurring
* [Data Access Object](#dao) * [Data Access Object](#dao)
* [Service Layer](#service-layer) * [Service Layer](#service-layer)
* [Naked Objects](#naked-objects) * [Naked Objects](#naked-objects)
* [Repository](#repository)
### Integration Patterns ### Integration Patterns
@ -670,6 +671,20 @@ validation and for building to order
**Real world examples:** **Real world examples:**
* [Apache Struts](https://struts.apache.org/) * [Apache Struts](https://struts.apache.org/)
## <a name="repository">Repository</a> [&#8593;](#list-of-design-patterns)
**Intent:** Repository layer is added between the domain and data mapping layers to isolate domain objects from details of the database access code and to minimize scattering and duplication of query code. The Repository pattern is especially useful in systems where number of domain classes is large or heavy querying is utilized.
![alt text](https://github.com/iluwatar/java-design-patterns/blob/master/repository/etc/repository.png "Repository")
**Applicability:** Use the Repository pattern when
* the number of domain objects is large
* you want to avoid duplication of query code
* you want to keep the database querying code in single place
* you have multiple data sources
**Real world examples:**
* [Spring Data](http://projects.spring.io/spring-data/)
# Frequently asked questions # Frequently asked questions