Database Management Systems

Introduction

A DBMS is the software that runs your database — it accepts SQL, manages files on disk, handles concurrent users, enforces constraints, replicates data and recovers from crashes. The most popular open-source DBMSs are PostgreSQL and MySQL; commercial ones include Oracle and SQL Server.

Beginner analogy: the database is the library; the DBMS is the staff that runs the library — checking books in/out, organizing shelves, and locking the doors at night.

Understanding the topic

Core concepts to understand:

• Storage engine — how rows are written to disk (InnoDB, heap...).
• Query engine — parses, plans and executes SQL.
• Transaction manager — ACID, locks, isolation.
• Replication — keeps copies on standby servers.
• Recovery — write-ahead log + crash recovery.

Syntax reference

Visual workflow / architecture:

┌─────────────────────────────┐
│           DBMS              │
├─────────────────────────────┤
│ Connection Pool             │
│ Parser → Planner → Executor │
│ Buffer Cache                │
│ Storage Engine              │
│ WAL (Write-Ahead Log)       │
│ Replication / Backup        │
└──────────┬──────────────────┘
           ▼
       Disk Files

Real-world use

PostgreSQL runs Reddit, Instagram, Apple's iCloud metadata, and most fintech ledgers. MySQL powers Facebook, GitHub, Booking.com and Shopify. Both can scale to billions of rows.

Best practices

• Always understand which DBMS you're targeting — features differ.
• Use connection pooling — never open a fresh connection per request.
• Configure WAL & backups before going live.

Hands-on exercise

Interview preparation — practice these questions:

• Q1. What is a DBMS?
• Q2. Difference between a DBMS and a database.
• Q3. Name three open-source and three commercial DBMSs.
• Q4. Role of the WAL.
• Q5. Why use connection pooling?