16-lesson production course

Build Spring backends that remain explainable under failure.

Follow one flash-sale order service from its HTTP boundary to its durable state, security policy, operational evidence, production-like tests, and incident recovery loop. Each module states what its evidence proves—and what it cannot prove.

Three ordered modules

Trace the production boundary, not just the annotation.

Complete the lessons in order so later transaction, operations, and recovery decisions retain the same incident context.

Module 03 · 9 lessons

Security, operations, testing, and recovery

Deny access by default, expose bounded operational evidence, prove production-sensitive behavior against PostgreSQL, and recover from incidents deliberately.

  1. Spring Security Filter Chain and Authorization Explained
  2. Spring Boot Actuator, Health, and Metrics Explained
  3. Spring Boot Integration Testing with Testcontainers Explained
  4. Production Spring Boot Incident Troubleshooting
  5. Java Virtual Threads for Backend Services
  6. Production Java Concurrency Troubleshooting
  7. Production JVM Performance Diagnostics Explained
  8. Java Heap Dumps and Memory Leak Analysis
  9. Evidence-Based JVM Tuning and Capacity Verification

Course library

Review every Spring Backend lesson.

Use these article cards for direct access while preserving the ordered modules above as the primary study sequence.

FAQ

Spring Backend course questions

What does the Spring Backend course cover?

It connects Spring MVC, validation, transactions, JPA, security, Actuator, Testcontainers, JVM diagnostics, and incident response through one production order-service scenario.

Which Spring Boot version does the course use?

The new production lessons document Spring Boot 4.1 as the mainline and call out Spring Boot 3.5 compatibility boundaries that teams must verify against their selected dependencies.

Does the course include the existing REST controller lesson?

Yes. The REST controller lesson remains a cross-reference in API Design while becoming the controller foundation inside this Spring Backend sequence.