gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
java-design-patterns/repository
History
Anurag Agarwal 20ea465b7f Java 11 migrate remaining q-r (#1121) 
* Moves queue-load-leveling to Java 11

* Moves reactor to Java 11

* Moves reader-writer-lock to Java 11

* Moves repository to Java 11

* Moves resource-acquisition-is-initialization to Java 11

* Moves retry to Java 11

* Moves role-object to Java 11
2020-01-04 18:43:12 +02:00
..
etc
#1113 Add uml-reverse-mapper plugin
2019-12-07 18:03:49 +02:00
src
Java 11 migrate remaining q-r (#1121)
2020-01-04 18:43:12 +02:00
pom.xml
Issue 989 final-batch (#1119)
2019-12-29 14:41:21 +02:00
README.md
https://github.com/iluwatar/java-design-patterns-web/issues/8 Update pattern categories and tags
2019-12-13 21:09:28 +02:00

README.md

layout, title, folder, permalink, categories, tags
layout title folder permalink categories tags
pattern Repository repository /patterns/repository/ Architectural
Data access

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.

Class diagram

alt text

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

Credits