Backend Development
8 clusters, spanning half-life layers 1–3: Python frameworks, JS/TS backend, JVM backend, Go backend, .NET backend, Rust backend, Ruby & PHP, Cross-cutting concerns.
Clusters
Section titled “Clusters”Python frameworks
Request lifecycle, middleware, ORM/serialisation boundary and dependency wiring transfer across all four. Django’s batteries-included conventions do…
JS/TS backend
Middleware composition and the handler signature transfer trivially between all of them. NestJS’s decorator/DI model is a different paradigm and…
JVM backend
Dependency injection, the bean lifecycle and declarative configuration transfer across all of them. Startup model and reflection strategy differ…
Go backend
net/http’s Handler interface is the substrate every member wraps, so it transfers to all of them. Routing DSLs and middleware signatures do not..NET backend
Single-member in practice. The middleware pipeline and DI container transfer to Spring conceptually; nothing else does.
Rust backend
The async runtime (Tokio) and the ownership implications of shared state transfer across all three and are the real content. Extractor and handler…
Ruby & PHP
Convention over configuration, the ActiveRecord pattern and the full-stack MVC shape transfer between Rails and Laravel almost line for line. Symfony…
Cross-cutting concerns
Layer 1 and the highest-value part of the domain: every one of these is the same problem in every framework, and learning it once means every later…