database

A program that stores data in an organised way and answers questions about it, such as PostgreSQL.

In more detail

A database keeps data on disk so it survives restarts, lets many programs read and change it safely, and answers questions you ask in a query language. Relational databases such as SQLite and PostgreSQL store data in tables and are queried with SQL; other kinds store documents, key-value pairs or graphs.

Examples

A Bloom filter in front of a database skips queries for keys that are certainly absent.
In the course inventory, dbservers is a group of database hosts that share a data directory.
In the APIs course: The course service keeps its tasks and owners in a small SQL database.
In AWS you can run a database yourself on EC2 or use a managed service such as Amazon RDS or DynamoDB.
A self-hosted runner can reach a database that only answers inside your own network.
Module six shows why writing to a database and to Kafka separately is unsafe.
In the twelve-factor app a database is a backing service reached through a handle in config, and stateless processes keep anything that must persist in it. Database schema changes need compatibility planning in rolling and blue-green releases.
Linux keeps several small databases as files: the account database in /etc/passwd and /etc/group, and each package manager's record of installed packages. Larger systems use database servers such as PostgreSQL. Either way, change them through the tools meant for them rather than by hand.
Server Components can query the database directly; the connection code must stay server-only.
The course trace has a SELECT basket child span with db.system="postgresql".
A metrics page must never query a database while it is being built.
Serious web sites store shared data in a database; the course's name list page uses a text file instead.
A slow database query behind one widget should not hold up the whole page; give it its own Suspense boundary.
Recovery reconnects the database tier first, then applications, then users.
The SQL course compares SQLite, which runs every exercise, with PostgreSQL.
In Terraform: Databases are the resources where a careless replacement or destroy costs the most, because the data goes with them. Read any plan touching one twice.
In this course: A fake or in-memory stand-in can test business rules quickly, but only the real database engine can prove that your SQL is valid, constraints are enforced, migrations apply and transactions isolate correctly. Give each test its own data through a rolled-back transaction, a fresh schema or a disposable database.

Related terms

Taught in

References

Certification courses