Databases underpin almost every modern application by
organising and storing data in structured
ways. Relational databases, developed in the 1970s,
organise data into tables with rows and
columns and enforce a predefined schema. Tables are
linked through foreign keys, enabling
Database Systems:complex queries using
Relational
Relational systemsvs
Structured Query Language (SQL).
offerNoSQL
strong
consistency and support ACID (Atomicity, Consistency,
Isolation and Durability) properties,
making them ideal for financial transactions and
enterprise systems. Popular relational
databases include MySQL, PostgreSQL and Oracle. NoSQL
databases emerged to address limitations
in scalability and flexibility. They eschew rigid schemas
and use models such as key value
stores, document stores, wide column stores and graph
databases. NoSQL systems prioritise
availability and partition tolerance (as described by the
CAP theorem) and often follow the
BASE (Basically Available, Soft state, Eventually
consistent) model. Examples include MongoDB
(document oriented), Cassandra (wide column), Redis
(key value) and Neo4j (graph). Key
distinctions include data model (structured tables versus
flexible documents), scalability
(vertical versus horizontal), query languages (SQL versus
custom APIs), transaction semantics
(ACID versus eventual consistency) and typical use cases.
Relational databases excel at complex
joins and structured data, whereas NoSQL databases
handle large volumes of semi structured or
unstructured data and support high write throughput.
Some modern systems, called NewSQL, aim to
combine strong consistency with horizontal scalability.
Choosing between relational and NoSQL
depends on the application s requirements for
consistency, schema flexibility, performance and
scaling.