Doing backend work in Java? Start here. This is the Spring Boot material, and it’s the deepest framework section in the vault — ~3,000 words distilled from a real Spring Boot payment sandbox, not from documentation.
Concurrency model: thread-per-request. Spring MVC on a servlet container gives every request its own OS thread — simple to reason about, expensive at scale. From Java 21, virtual threads turn it into green threads without a code change, which is the biggest thing to happen to Java backends in a decade. Spring WebFlux is the event-loop/reactive alternative, and Loom has largely removed the reason to reach for it: you can now get the scalability without the reactive programming model. → runtime & concurrency models
Reading order
- Spring Boot & Scheduling — [Intermediate] — what the framework actually does for you, dependency injection, controller/service/store layering, validation,
ResponseEntity,HandlerInterceptor,@Asyncoffloading,@Scheduledjobs, and a retry state machine - The Java Web Landscape — [reference] — Quarkus, Micronaut, Javalin, Play: what each optimises for, and why the GraalVM native-image push exists
- API Design & Documentation — [Intermediate] —
RestTemplatefor outbound calls, the config-resolution/fallback pattern, business codes over raw HTTP status, and OpenAPI/springdoc
Where this moved from, and why
These three notes used to live in languages/01-java/05-web-and-api/. They were moved here, not copied — there is exactly one copy of this material and it is this one.
The reason is a rule that now applies across the vault:
languages/teaches the language.backend/frameworks/teaches the frameworks built on it.
So languages/01-java/ keeps the JVM, concurrency, generics, collections, tooling and persistence — the things true of Java whether or not you ever serve an HTTP request. Spring Boot is a web framework, and it belongs next to Express, Nest, Axum and Gin, where you can compare them.
That comparison is the point. Spring’s @RestController / @Service / @Repository and Nest’s @Controller / @Injectable are the same idea with different spelling — which is obvious when they sit in one folder and invisible when they’re filed under different languages. See the translation table in frameworks/.
What you still need from languages/01-java/
Spring Boot sits on top of Java, so the language material is a genuine prerequisite rather than a cross-reference:
- Dependency Injection — the container concept, pulled out from under the framework
- JVM & Concurrency — what thread-per-request and virtual threads actually mean
- Persistence — JDBC and JPA, the layer under
@Repository - Build Tools — Maven/Gradle, and how Spring Boot’s plugin packages a fat jar
- Testing —
@SpringBootTest,@WebMvcTest,@DataJpaTestslices
Related
- frameworks/ — the same concepts across every stack
- Structuring a Backend — the layering Spring’s annotations name
- Java course — the language underneath
- Spring interview prep
- direct-debit-sandbox — the project this material came from
Software engineering
Infrastructure & security
Computer science
Hardware & engineering