Relational model
The relational model represents data as relations—sets of tuples over defined attributes—and provides principles for manipulating and constraining those relations.
Grokking Software Architecture
A data model that represents information as relations, commonly implemented as tables linked through shared values.
- How it is used
- Introduces relational databases as an alternative to navigating physical record paths.
- How deep it goes
- Explains tables, keys, normalization, and declarative retrieval without formal set-theory derivations.
- Examples
- Illustrates customer orders linked by Customer_ID and an address-update anomaly.
- What you can do after
- Evaluate and understand how linked tables and normalization address data organization and update anomalies.
Read how Grokking Software Architecture explains relational model →
Java Persistence with Spring Data and Hibernate epub
The relational data model represents information as relations consisting of tuples and attributes with defined integrity constraints.
- How it is used
- Provides a shared, integrity-preserving foundation for representing business entities and persisting application data.
- How deep it goes
- Explains integrity, independence, SQL operations, and JDBC access, but stops short of relational execution internals.
- Examples
- Uses DDL, DML, DQL, DCL, joins, aggregation, subselects, and JDBC result-set processing as concrete applications.
- What you can do after
- Apply it via SQL and JDBC while recognizing when object-persistence frameworks or alternative consistency models are appropriate.
Read how Java Persistence with Spring Data and Hibernate epub explains relational model →
Functional Design and Architecture: Examples in Haskell
A data model that represents information as relations, typically implemented as tables whose structure is defined by a relational schema.
- How it is used
- Positions relational models as database representations that persist domain information and connect application code with relational storage.
- How deep it goes
- Defines tables, schemas, references, and implementation trade-offs, but stops short of detailed relational algebra or query construction.
- Examples
- Uses table schemas, database-subsystem layers, Haskell SQL connectors, beam, Selda, Esqueleto, and Higher-Kinded Data.
- What you can do after
- Evaluate relational-model designs and choose among SQL connectors, mapping layers, and schema representations while recognizing coupling costs.
Read how Functional Design and Architecture: Examples in Haskell explains relational model →
Also covered in
What to know first
- SQLSQL is a standardized declarative language for defining, querying, and manipulating data in relational database systems.
- database tableA database table is a relational data structure that organizes records into rows whose values correspond to defined columns.
Related concepts
- domain modelcontrasts with · A domain model is a software representation of the concepts, entities, relationships, rules, and behavior of a problem domain.
- graph databasecontrasts with · A graph database is a database system that represents data as entities and their relationships, typically using nodes and edges, and supports queries over that structure.
- normalized tableuses · A normalized table is a tabular representation that organizes related attributes into focused relations or fields to reduce redundancy and prevent dependency anomalies.
- key-value storealternative to · A key-value store is a data-storage system that associates keys with values and supports storing, retrieving, or updating values by key.
Questions about relational model
What is relational model?
The relational model represents data as relations—sets of tuples over defined attributes—and provides principles for manipulating and constraining those relations.
Which Manning books explain relational model?
Grokking Software Architecture, Java Persistence with Spring Data and Hibernate epub and Functional Design and Architecture: Examples in Haskell.
What should I know before learning relational model?
Manning books that teach relational model usually introduce SQL and database table first.
What is the difference between relational model and domain model?
The relational model represents data as relations—sets of tuples over defined attributes—and provides principles for manipulating and constraining those relations. A domain model is a software representation of the concepts, entities, relationships, rules, and behavior of a problem domain.
What is relational model a kind of?
Relational model is a kind of model. A model is an abstract representation of a system, phenomenon, application, or domain that captures relevant structure, behavior, data, or beliefs.
What is relational model also called?
Relational model is also called relational data model.
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.


