A database design approach that organizes data into tables (relations) with rows and columns, establishing relationships between tables through keys to ensure data integrity and minimize redundancy. Rooted in E. F. Codd's relational model, it underpins SQL databases and much of how APIs expose and constrain the data behind them.
Relational Data Modeling
Relational Data Modeling is the discipline of structuring data into tables — called relations — of rows and columns, then wiring those tables together with primary and foreign keys so that facts are stored once and joined as needed. Introduced by E. F. Codd in 1970, the relational model became the foundation for SQL and remains the default way most operational data is organized. A good relational model minimizes redundancy, enforces integrity, and makes the meaning of the data explicit.
- Tables and keys - Data lives in relations, and primary/foreign keys express how one relation refers to another.
- Normalization - A set of rules that eliminates duplicate data and update anomalies by decomposing tables into their natural parts.
- Entity-relationship design - Entities, attributes, and relationships are mapped out — often as an ER diagram — before any table is created.
- Integrity constraints - Uniqueness, referential, and check constraints let the database itself guarantee that the data stays valid.
The relational model rarely disappears when you put an API in front of it — it just gets reshaped. The way an API represents resources, nests related objects, and validates payloads through JSON Schema and OpenAPI usually traces back to an underlying relational design, and leaky abstractions between the two are a common source of awkward API contracts. Understanding the data model behind an API is often the fastest way to understand the API itself, which is why relational modeling remains a quiet prerequisite for good API design and governance.
