The section that makes this a course rather than a framework tutorial. Every backend, in every language, faces the same structural questions — and the answers are the same whether you’re writing NestJS, Spring, FastAPI, or Axum. Frameworks disagree about syntax and agree almost entirely about shape.
Read in order; each note assumes the previous.
-
Layers — Controllers, Services, Repositories — [Beginner→Intermediate] — the three jobs every backend separates, the rule that tells you when you’ve broken it, and the honest caveats (anaemic pass-through services, the “swappable database” myth)
- …in other languages — [Beginner→Intermediate] — each framework’s names for the layers, and exceptions vs error values vs
Resultvs return codes for domain errors
- …in other languages — [Beginner→Intermediate] — each framework’s names for the layers, and exceptions vs error values vs
-
Organising by Layer vs by Feature — [Beginner→Intermediate] — the folder argument that isn’t bikeshedding: change locality, deletability, and how
shared/rots- …in Go, Java, Rust, C, C++ and C# — [Intermediate] — the companion: where the compiler or build system enforces the boundary itself, and why by-layer switches it off
-
Dependency Injection & Wiring — [Intermediate] — being handed your tools instead of making them; constructor injection, when interfaces earn their keep, and the scope bugs
- …in other languages — [Intermediate] — Spring and .NET containers, Go and Rust by hand, C’s function-pointer structs, and which languages catch the scope bug
-
Hexagonal & Clean Architecture — [Intermediate→Advanced] — inverting the dependency so business rules depend on nothing; four names for one idea, and an honest account of what it costs
- …in other languages — [Intermediate→Advanced] — ports per language, and making the build enforce the dependency rule
-
Modular Monolith → Services — [Intermediate→Advanced] — where boundaries actually belong, why to discover them in the cheap medium first, and what changes the moment a call crosses a network
- …in other languages — [Intermediate→Advanced] — each ecosystem’s event plumbing, and the idempotent consumer in seven languages
The through-line
All five notes are one question at different scales:
What depends on what, and can you change one thing without changing everything else?
- Note 1: within a request — the controller depends on the service, not the reverse.
- Note 2: within a codebase — a feature’s files depend on each other, not on every other feature.
- Note 3: within a class — declare what you need instead of constructing it.
- Note 4: within an application — the domain depends on nothing.
- Note 5: within a system — a module’s boundary is a function call or a network call.
Get the direction of dependency right and most structural questions answer themselves.
The pragmatic summary
If you read nothing else: default to layered + by-feature + constructor injection. Add hexagonal only where the business rules are genuinely complex. Stay a modular monolith until you have a named reason to split — and enforce your module boundaries with a linter, because boundaries maintained by discipline don’t survive a deadline.
Related
- Backend course · 01 — Foundations
- frameworks/ — how Nest, Spring, FastAPI and others implement all of this
- Architecture — the same questions at system scale
- Design Patterns — repository, adapter, facade
Software engineering
Infrastructure & security
Computer science
Hardware & engineering