0 of 4 done
Start hereWhat a Backend Actually Is

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.

  1. What a Backend Actually Is — [Beginner] — the four responsibilities, the “never trust the client” rule everything follows from, and where the frontend boundary sits
  2. HTTP Servers — [Beginner] — how requests physically arrive and get dispatched
  3. The Request Lifecycle — [Beginner→Intermediate] — the nine stages every framework implements, the middleware onion, and a symptom→stage debugging table
  4. 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.

↑ Back to Backend