Skip to main content
Definition Website Computer and Technology

Relational Database

Subject: Computer and Technology noun /rɪˈleɪ.ʃən.əl ˈdeɪ.təˌbeɪs/ 1 definition

  1. Definition (noun)

    Entry #62 · Updated

    A Relational Database is a structured data store based on the relational model, representing entities as tables composed of typed columns (attributes) and rows (records or tuples). Each table enforces a predefined schema and connects to other tables through primary keys and foreign keys, maintaining referential integrity, reducing redundancy through normalization, and enabling declarative, set-based queries via Structured Query Language (SQL). Typically managed by a Relational Database Management System (RDBMS) with ACID (Atomicity, Consistency, Isolation, Durability) transaction guarantees, it prioritizes data consistency and structured relationships over schema-free document or unstructured object storage.

    Common Types

    • Transactional (OLTP) Databases: Row-oriented engines such as PostgreSQL and MySQL optimized for high-concurrency, low-latency reads, writes, and point lookups with strict ACID guarantees.

    • Analytical (OLAP) Databases: Column-oriented engines such as Amazon Redshift and Snowflake engineered to run complex joins and aggregations rapidly across massive historical datasets for reporting and business intelligence.

    • Embedded Relational Databases: Lightweight, serverless libraries such as SQLite that run directly inside an application process and persist structured tables in a single local file without a separate database server.

    • Distributed SQL Databases: Horizontally scalable relational systems such as CockroachDB and Google Spanner that shard and replicate tables across multiple nodes using consensus protocols while preserving SQL semantics and distributed ACID transactions.

    Example

    In an online bookstore's PostgreSQL database, a customers table identifies each shopper with a primary key customer_id, and an orders table references that column via a foreign key constraint to prevent orphaned purchases. During checkout, the database wraps inventory updates and order insertion in a single ACID transaction, and accounting queries later combine records from customers, orders, and books using a SQL JOIN.