Repository pattern

As explained in Effective Platform Engineering

A repository layer is an architectural layer that exposes datastore operations through repository abstractions to higher layers.

The repository pattern places a repository layer between services and datastore implementations, exposing consistent operations while hiding database-specific details. This abstraction supports cloud or database migration without rewriting service code. section 2.3.3

A platform can provide datastore implementations and repository abstractions for supported technologies. Services call repository functions; repositories call a datastore interface selected for the required cloud and database. section 2.3.3

Figure 2.12 When a particular service within the API needs to interact with the API database, it calls a repository function that provides all the normal database methods. The repository function would call the datastore functions for the type of database the API needs to use (relational or unstructured, in our case).

Trace how service database calls pass through repository functions to relational or unstructured datastore implementations. section 2.3.3

Cloud and database migration

A service can move between GCP and another cloud, or change from AWS RDS for PostgreSQL to Aurora Serverless for MySQL, by rebuilding with a different datastore library. section 2.3.3

Validate the layering with architectural fitness functions:

• Allow handlers to access services, services to access repositories, and repositories to access datastores through explicitly defined layer rules. section 2.3.3

How Effective Platform Engineering covers it

How deep it goes

Explains the layer arrangement, interface boundary, migration effect, and automated architectural checks, without detailing repository method implementations.

Examples

Uses GCP migration, AWS RDS for PostgreSQL, Aurora Serverless for MySQL, relational and unstructured datastores, and layered pseudocode.

What it assumes

Assumes familiarity with service layers, datastores, interfaces, and cloud technologies; teaches their dependency boundaries through the architecture.

What you can do after

Apply it via repository and datastore interfaces to change supported databases or clouds while minimizing service rewrites.

How it connects

Connects repository layers with datastore interfaces, service layers, architectural fitness functions, cloud migration, and database abstraction.

liveBookmanning.com

Read Effective Platform Engineering on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Spring in Action, Sixth EditionA repository interface is an interface that declares data-access operations for an entity while leaving their persistence implementation to a supporting framework.
• 

  liveBookmanning.com
  Learn Go with Pocket-Sized ProjectsThe repository pattern is an abstraction that mediates between an application’s domain model and persistent data storage.
• 

  liveBookmanning.com
  Unit Testing Principles, Practices, and PatternsA repository is an abstraction that provides access to and modification of persisted data for a particular domain object or aggregate.
• 

  liveBookmanning.com
  Quarkus in ActionThe repository pattern encapsulates data-access operations behind an abstraction that manages persistence and retrieval for domain objects.
• 

  liveBookmanning.com
  Pro Angular 16A repository is an abstraction that mediates access to data while hiding how that data is obtained from application components.
• 

  liveBookmanning.com
  .NET in Action, Second EditionThe repository pattern is an architectural pattern that encapsulates access to and persistence of domain entities through a collection-like interface between the domain model and data-mapping or persistence layers.
• 

  liveBookmanning.com
  AI-Powered Developer: Build software with ChatGPT and CopilotThe Repository Pattern is a software design pattern that encapsulates data-access operations behind an interface separate from application logic.
• 

  liveBookmanning.com
  Simple Object-Oriented Design: Create clean, maintainable applicationsA repository is a component that encapsulates the logic for retrieving and persisting domain information.

Compare how 9 books explain repository pattern →

Related concepts

• Spring Data RESTused by · Spring Data REST is a Spring Data project that exposes repository-backed data and operations through RESTful resources.
• databaseuses · A database is an organized collection of persistent data managed by software for storage, retrieval, querying, and modification.
• active record patternalternative to · The Active Record pattern combines an object representing a persistent data record with operations for querying, storing, updating, and deleting that record.
• methodhas part · A method is a callable operation associated with an object or type and invoked through that association.
• domain modelcontrasts with · A domain model is a software representation of the concepts, entities, relationships, rules, and behavior of a problem or business domain.
• database transactionuses · A database transaction is a logical unit of database operations whose changes are committed together or rolled back as a whole.

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.