liveBook · Manning

Data layer

Also called persistence layer, data access layer, database layer

A software architectural layer that mediates access to data by storing, retrieving, transforming, or exposing it to other components.

How 8 Manning books explain it

React in Depth

The data layer is the application-stack layer responsible for data management and state flow.

How it is used
Organizes data management and state flow separately from fetching and UI presentation in a React application stack.
How deep it goes
Works through a provider-and-hooks boundary and its remote-data redesign, then identifies missing pieces in an expense-tracker build.
Examples
Uses a list-and-detail application with four data hooks and a frontend-only expense tracker whose static data needs implementation.
What you can do after
Build it from scratch by defining a presentation-facing data API, then implementing state or server-backed behavior behind it.

Read how React in Depth explains data layer →

AI-Powered Developer: Build software with ChatGPT and Copilot

A data access layer is the part of an application responsible for communicating with data stores while isolating that communication from other application logic.

How it is used
Isolates asset CRUD and persistence details behind repositories used by application services.
How deep it goes
Defines generic typed CRUD contracts, in-memory implementation, and ORM-to-domain mapping without showing a persistent repository implementation.
Examples
Demonstrates BaseRepository, InMemoryAssetRepository, AssetManager delegation, and SQLAlchemy-style AssetModel and FundingDetailsModel classes.
What you can do after
Build it from scratch as a typed repository boundary with replaceable in-memory and persistent storage implementations.

Read how AI-Powered Developer: Build software with ChatGPT and Copilot explains data layer →

Spring Start Here, Second Edition

A persistence layer is a software layer responsible for storing and retrieving application data beyond the lifetime of a process.

How it is used
Implements application data storage and retrieval, with Spring Data reducing repeated database-access code.
How deep it goes
Explains repository contracts, CRUD, pagination, sorting, and query methods, but does not detail their implementations.
Examples
Uses JDBC, Hibernate, and MongoDB as technology examples, and names repository contracts such as CrudRepository.
What you can do after
Build a Spring persistence layer by declaring repository interfaces and selecting a Spring Data module for the persistence technology.

Read how Spring Start Here, Second Edition explains data layer →

The Well-Grounded Data Analyst

A data access layer is a software layer that reads, retrieves, and prepares data for other application components.

How it is used
Supports proof-of-concept applications by isolating data loading, filtering, selector preparation, and visualization from presentation.
How deep it goes
Demonstrates concrete helper-function responsibilities and reuse, but stops short of broader application architecture.
Examples
Uses Welsh property data, cascading location selectors, transaction charts, property-type summaries, and county price distributions.
What you can do after
Build reusable Python functions that load, filter, summarize, and visualize application data for an interface.

Read how The Well-Grounded Data Analyst explains data layer →

Grokking Software Architecture

A data layer isolates data access and persistence operations from other application responsibilities.

How it is used
Separates database access and persistence from application responsibilities and supplies implementations for higher-layer interfaces.
How deep it goes
Defines database access through ORM or SQL and distinguishes fetch/store mechanics from business decisions and policies.
Examples
Names Entity Framework or SQL for database access and repositories as fetch/store translators.
What you can do after
Apply it by keeping fetch/store mechanics in repositories and business decisions and transaction policies inside the core or application service.

Read how Grokking Software Architecture explains data layer →

Java Persistence with Spring Data and Hibernate epub

The persistence layer is the architectural layer responsible for loading and storing domain-model state in durable storage.

How it is used
Separates durable state management from presentation and business logic in a layered application.
How deep it goes
Defines responsibilities, transparent persistence, entity lifecycle, persistence contexts, and units of work without detailing provider-specific mappings.
Examples
Uses a layered-architecture figure, Item#calculateTotalPrice(), unit tests, entity classes, annotations, XML descriptors, and persistence contexts.
What you can do after
Apply it by separating domain tests from database integration and organizing JPA-based loading, storing, and lifecycle management.

Read how Java Persistence with Spring Data and Hibernate epub explains data layer →

Effective Platform Engineering

A datastore layer is an architectural layer that encapsulates access to a database technology.

How it is used
Encapsulates database access so services can move between supported clouds and database technologies with less rewriting.
How deep it goes
Defines datastore interfaces, technology-specific implementations, repository integration, and automated architectural checks.
Examples
Uses GCP migration, AWS RDS for PostgreSQL, Aurora Serverless for MySQL, and relational or unstructured datastore implementations.
What you can do after
Build portable services that switch supported database implementations through datastore-library changes and verify layer adherence automatically.

Read how Effective Platform Engineering explains data layer →

Financial AI in Practice

An architecture layer containing governed data assets and the processes that prepare them for analysis and modeling.

How it is used
Organizes governed financial data and prepares pipelines and features for downstream modeling.
How deep it goes
Details collection, storage, streaming, marts, transformations, and privacy controls, but does not provide implementation code.
Examples
Uses repayment histories, transaction logs, bureau scores, alternative signals, loan-application velocity, and volatility features.
What you can do after
Build data pipelines and engineered features for financial modeling, separating historical storage, real-time processing, and specialized marts.

Read how Financial AI in Practice explains data layer →

Also covered in

What to know first

Related concepts

Questions about data layer

What is data layer?

A software architectural layer that mediates access to data by storing, retrieving, transforming, or exposing it to other components.

Which Manning books explain data layer?

React in Depth, AI-Powered Developer: Build software with ChatGPT and Copilot, Spring Start Here, Second Edition, The Well-Grounded Data Analyst, Grokking Software Architecture, Java Persistence with Spring Data and Hibernate epub, Effective Platform Engineering and Financial AI in Practice.

What should I know before learning data layer?

Manning books that teach data layer usually introduce contract, business logic, object-relational mapper and container first.

What is data layer part of?

Data layer is part of four-layer architecture. A four-layer architecture organizes a system into four distinct layers, each with separate responsibilities.

What are the parts of data layer?

Data layer includes feature engineering and pipeline.

What is data layer also called?

Data layer is also called persistence layer, data access layer or database layer.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.