What a backend is, how a request physically arrives and is handled, and the concurrency model your framework sits on. Everything in the rest of the course assumes these four notes.
- What a Backend Actually Is — [Beginner] — the four responsibilities, the “never trust the client” rule everything follows from, and where the frontend boundary sits
- HTTP Servers — [Beginner] — how requests physically arrive and get dispatched
- The Request Lifecycle — [Beginner→Intermediate] — the nine stages every framework implements, the middleware onion, and a symptom→stage debugging table
- Runtime & Concurrency Models — [Intermediate] — ⭐ thread-per-request vs event loop vs green threads, and why backend frameworks differ at all
⭐ Note 4 is the highest-leverage note in the course. It’s what turns frameworks/ from twenty things to memorise into three ideas and twenty vocabularies.
Related
- Backend course · 03 — Structuring a Backend
- Networking — TCP, HTTP, and TLS underneath this
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering