What is a database and why does design matter
database definition, structured vs unstructured data, DBMS role, design vs implementation, cost of bad design, real-world consequences
What Is a Database?
A database is an organized collection of related data managed by a Database Management System (DBMS). The DBMS handles storage, retrieval, and integrity so your application code does not have to.
Compare this to storing everything in CSV files or JSON blobs. That works for toy projects. It breaks down when two users write simultaneously, when you need to enforce that every order has a valid customer, or when you query a million records. The DBMS solves all three.
Why Design Before You Build
Design is the step where you decide what tables exist, what columns they hold, and how they relate. Skipping it causes:
- Redundancy — same data stored in five places, updated in three.
- Anomalies — deleting an order accidentally deletes the only record of a customer.
- Impossible queries — you realize you never stored the data you need.
A schema change after launch is expensive. A schema change after millions of rows exist is painful. Getting the design right before writing a single CREATE TABLE is the cheapest thing you can do.
The Design Workflow
Good database design follows a repeatable path: gather requirements → identify entities and relationships → draw an ER diagram → normalize → write DDL. This course walks that entire path.