Foray / DatabasesDatabases roadmap Run data stores that people depend on: the relational and NoSQL models, installing and operating engines, performance, backups, replication and failover, migrations and security. isThisTutorial has no database course yet, so most of this map is honestly planned; what exists is the operational side.
11 topics · 57 nodes · 24 covered · 14 partly · 19 planned · updated 2026-10-17
Sign in with your Mycelium account to see which nodes you have finished.
Show Whole map Gaps only 1. Core
Data foundations How data is modelled and queried, before any engine.
0 / 5 covered
The relational model and SQL Planned Transactions, ACID and isolation Planned Consistency and the CAP trade-offs optional Planned Data modelling and normalisation Planned NoSQL data models Partly covered 2. Core
Database engines Learn one relational engine well; know the others exist.
0 / 6 covered
PostgreSQL pick one Planned Redis and in-memory stores optional Partly covered Search and analytics stores optional Planned MySQL and MariaDB pick one Planned MongoDB and document databases pick one Planned SQLite optional Planned 3. Core
Running databases Where the database lives and how it gets there.
4 / 6 covered
Managed databases on AWS (RDS) Covered Databases on Kubernetes Covered Provisioning with infrastructure as code Partly covered A database in Docker Covered Installing and configuring on a server Partly covered Disks, filesystems and I/O Covered 4. Core
Performance and capacity Fast enough, and enough room to grow.
0 / 6 covered
Indexes and query plans Planned Connection pooling Planned Capacity planning Partly covered Query and schema tuning Planned Monitoring databases Partly covered Caching in front of the database Partly covered 5. Core
Backup and recovery The job nobody notices until the day it matters most.
5 / 6 covered
Why backups, RPO and RTO Covered Point-in-time recovery Partly covered Managed and cloud backups Covered Database backups Covered Restore testing Covered Immutable and encrypted backups Covered 6. Core
Replication, failover and disaster recovery Keep serving when a server, a zone or a region fails.
4 / 5 covered
Replication and failover Covered Multi-region data Covered Partitioning and sharding optional Planned High availability on AWS Covered Disaster recovery strategies Covered 7. Core
Schema changes and releases Change the schema without downtime or data loss.
3 / 5 covered
Database migrations Covered Expand and contract Partly covered Idempotency and data consistency in applications optional Covered Stateful and data-heavy releases Covered Migrations in CI/CD Partly covered 8. Core
Database security Data stores hold the valuable things.
3 / 6 covered
Roles, privileges and least privilege Partly covered Encryption at rest and in transit Covered Auditing and data masking Partly covered Credentials and secrets Covered Network isolation Covered Privacy and retention Partly covered 9. Recommended
Cloud data services The managed menu: pick the store that fits the access pattern.
4 / 6 covered
Relational databases (RDS) Covered Object, block and file storage Covered Data warehouses and analytics optional Planned DynamoDB Covered Queues and event streams Covered Azure SQL, Cloud SQL and Spanner pick one Planned 10. Recommended
Cost of data Storage, I/O and transfer add up quietly.
1 / 2 covered
Storage and data-transfer costs Covered Rightsizing and commitments Partly covered 11. Optional
Data engineering Beyond serving applications: moving and analysing data.
0 / 4 covered
ETL, ELT and pipelines Planned Data lakes and lakehouses Planned Streaming with Kafka Planned Data for machine learning Planned © 2026 Konstantinos Maglaras
