Free courses · 18 puzzles · 5 practice chapters · Final project
Backend engineering from first request to production
Learn to design, build, test and operate a bookmark API. Start with a local request, then work through databases, identity, caching, Docker, Kubernetes and a release project.
Course outline
Build and test your first service3 puzzles
Start with one request, one durable row and a test.
- What happens when a client sends a request? Follow one bookmark from a client to the process that owns it.
- Did the first write happen? Make a lost reply safe to retry.
- Can two clients prove the rule? Test a retry through the running service and read what survived.
Release and recover a first version2 puzzles
Follow the same row through a release and a storage incident.
- Where does the data live during a release? Replace the running service while keeping its bookmark file.
- Alive, ready, or serving the wrong thing? Diagnose a storage failure and rehearse recovery.
API contracts and relational databases4 puzzles
Validate inputs, model owners, commit related changes and paginate results.
- Can an old client read the new response? Define the shape and meaning of a request before changing it.
- Can a bookmark point to a missing owner? Model relationships and query accounts that have no saved rows.
- What if the service stops between two writes? Save the bookmark and the work it creates together.
- Why does the same page cost less to read? Inspect a query plan before and after adding an index.
Identity and changes over time4 puzzles
Limit access by owner, expire sessions, refresh caches and migrate data.
- Whose bookmark may this request read? Trace identity from the caller to the storage query.
- Who vouched for the caller? Follow a session from an identity check to permission on one row.
- When does a reader see yesterday’s list? Predict the exact interval during which a saved response can be stale.
- Can two releases share one schema? Change the shape of stored data while an older reader is still running.
Docker, Kubernetes and production operations4 puzzles
Package the service, replace a pod, measure performance and deliver your final project.
- What goes in a Docker image? Predict which files a replacement container can read and write.
- Who replaces a missing pod? Watch a local cluster restore a process and inspect what survives.
- Which users felt the slowdown? Compare request durations, failures and resource pressure.
- What evidence earns a release? Ship a change with tests, a recovery path and a capacity argument.
Concurrent edits1 puzzles
A check at save time that detects a change since the client read a record.
- What does the second editor see? Follow two clients editing the same saved title.
Practice chapters
- Reading production evidence
- Build and roll out a service under resource limits
- Follow one booking through Spring MVC and a database transaction
- Diagnose a running Docker container
- Build a SQL report that survives awkward data
Final project
Release a bookmark editor without losing either draft · Produce a release packet for an editor shared by two clients. Demonstrate a version conflict, verify committed state, then decide whether the release can be rolled back.
How the course works
Start with one request. In each lesson, predict the result, run the browser experiment and change one condition. The local project then asks you to build the service, run its tests, deploy it and recover its data.
Every puzzle is open from this outline. The check at the end of a puzzle unlocks its next button and saves your progress in this browser.
Take it with you
Continue with Claude
Copies a prompt that turns Claude into your tutor for this course: what you've passed, the words you know, the questions you slipped on, and how to teach you, one small block at a time. Paste it into Claude, or any AI assistant. Built in your browser from your progress; nothing is sent anywhere.
Download for Obsidian
The whole course as an Obsidian vault: a note per puzzle linked to the puzzles it builds on (open the graph view to see the building blocks), practice chapters with worked cases, a final project, a glossary, and puzzle flashcards for the Spaced Repetition plugin.