Relational Databases for Backend Developers
Relational databases store data in tables with rows and columns linked by keys, and are queried with SQL. Good schema design uses normalisation, primary and foreign keys and constraints, transactions give ACID guarantees, and indexes and query plans determine performance. PostgreSQL and MySQL are common choices.
Stage: Databases · Part of the Backend Developer roadmap · Last reviewed 19 November 2026
What to learn in Relational Databases
- Write SELECT queries with joins, grouping and filters
- Design a normalised schema with primary and foreign keys
- Wrap related updates in a transaction and roll back on error
- Explain atomicity, consistency, isolation and durability
- Add an index and confirm its use with EXPLAIN
Relational Databases interview questions
What does ACID stand for?
Atomicity means a transaction fully happens or not at all. Consistency means it moves the database from one valid state to another. Isolation means concurrent transactions do not see each other's partial work. Durability means committed data survives crashes.
How does an index speed up a query and what is the cost?
An index, usually a B-tree, lets the database find matching rows without scanning the whole table. The cost is extra storage and slower inserts and updates, since each index must be maintained. Index columns used in frequent filters, joins and sorts.
Where Relational Databases fits in the Backend Developer roadmap
Relational Databases belongs to the Databases stage (beginner level), which takes about 5 hours. Model, query and tune data stores.
Other units in this stage
Back to the full Backend Developer roadmap