I run production databases for a living. PostgreSQL, MySQL, MongoDB, Aurora. Ten years of it.
This site is the page I wished someone had handed me when I started. It starts with the files on disk. It ends with the check you run at 2 AM.
A page at 2 AM. A query that was fine yesterday and slow today. A disk that filled up while nobody was watching. A replica that was three seconds behind and a user staring at data they had just saved.
Nobody handed me a page that started with the files on disk. So I wrote one.
This site teaches three databases the way they actually exist on a server. A process, a block of memory, and a directory of files. If you know where the bytes sit, the performance follows. If you do not, you are guessing, and guessing is how you end up restarting a database at 2 AM hoping the problem goes away.
It goes from zero to staff level. The facts are the same at every level. Only the questions get harder.
Start at Home if you are new. It follows one insert from the app to the log file to the data page to the replica, then walks through a read, an update, a delete, and a crash.
Follow the Staff Path if you want the guided route. It goes from zero to staff level in order, one problem and one diagram at a time.
Keep the Cheat Sheet open if you already know the ideas and need the numbers. Three sheets, one per engine, eight rules each.
If something is broken right now, skip the reading. Go to the incident cards on Home. Find your symptom. Run the check named beside it.
Before you leave, check this: run EXPLAIN (ANALYZE, BUFFERS) on your slowest query. Look at the pages it read. That number tells you what to fix.