What Spring Boot Adds
Separate Spring Framework from Boot, then trace starters, SpringApplication, component scanning, conditional auto-configuration, and back-off behavior.
Start with object construction, the IoC container, lifecycle, and proxies. Then use that runtime model to understand Boot, MVC, JPA, security, testing, and production behavior.
Your Course Track
Begin with Stage 1: Core Spring & Mental Models to understand object construction, the IoC container, and bean lifecycles.
Core curriculum
Each stage owns its concepts once. Later lessons link back to the runtime model instead of explaining the same annotation again.
Separate Spring Framework from Boot, then trace starters, SpringApplication, component scanning, conditional auto-configuration, and back-off behavior.
Begin with ordinary Java object construction, then see why IoC, dependency injection, XML bean definitions, Java configuration, and component scanning exist.
Externalize settings, bind validated properties, select profiles, and keep secrets outside the artifact before infrastructure depends on them.
Place controllers, application services, repositories, DTOs, validation, and error translation at explicit boundaries.
Connect database behavior to JPA, Hibernate, Spring Data repositories, the persistence context, fetching, transactions, locking, and query performance.
Write structured, correlated logs and expose safe health, metrics, and tracing signals before tuning or distributing the system.
Choose the smallest useful test boundary: plain unit tests, collaboration tests, MVC/JPA slices, full application tests, or real infrastructure.
Trace authentication and authorization through the SecurityFilterChain before comparing sessions, JWT, CSRF, CORS, and OAuth 2.0/OIDC.
Call external services safely and add caching only after defining timeouts, retries, idempotency, consistency, and failure evidence.
Package, observe, test, and deploy one modular application before considering distributed-system complexity.
Course curriculum
Opening a module takes you to its own workspace—other modules stay out of the way.
Confirm the main Java, backend, and tooling basics before starting Spring Boot.
Know the core Java, HTTP, SQL, and build-tool concepts needed to follow the Spring Boot modules.
Prerequisite: None
Separate the Spring portfolio, Spring Framework, and Spring Boot, then trace how Boot assembles a conventional application.
Explain which capabilities come from Java, Spring Framework, Spring Boot, and other Spring projects—and organize a project so Boot can discover it predictably.
Prerequisite: Module 0 readiness checkpoint
Start with ordinary Java object construction, follow Spring configuration from XML to annotations, and inspect how the container turns bean definitions into managed objects.
Explain why Spring exists, how configuration metadata becomes BeanDefinition objects, and how the container creates, wires, initializes, and sometimes proxies a bean.
Prerequisite: Spring Boot fundamentals
Externalize every environment difference—properties, YAML, profiles, typed configuration binding, and secrets that never touch version control.
Ship one artifact into dev, test, and production with only the environment changing, and keep credentials out of the repository.
Prerequisite: Spring Boot fundamentals
Build a task API end to end: controllers, request binding, DTO boundaries, status codes, validation, pagination, and the MVC internals underneath.
Ship endpoints with validated input, consistent error payloads, and tests that prove the HTTP contract.
Prerequisite: Spring Core and configuration
Turn malformed input and domain failures into predictable, machine-readable API contracts.
Design validation boundaries and one safe error vocabulary for every endpoint.
Prerequisite: Spring MVC
Stop putting everything in controllers: split responsibilities across controller, service, repository, and DTO layers and organize packages so structure follows intent.
Refactor an endpoint-heavy prototype into a layered service where each class has one reason to change.
Prerequisite: Spring MVC and validation
Model entities honestly, choose fetch strategies deliberately, and keep every write inside a transaction scoped to one business operation.
Persist and query data without N+1 surprises, leaked entities, or accidental multi-statement commits.
Prerequisite: Application architecture and SQL fundamentals
Build a fast confidence system with pure unit tests, focused Spring slices, and realistic container-backed integration tests.
Choose the narrowest test that can prove each risk and keep the suite deterministic.
Prerequisite: Spring MVC and Spring Data JPA
Trace authentication and authorization through the servlet filter chain, then build session, bearer-token, and OIDC security deliberately.
Secure an API with least-privilege rules and explain every trust boundary.
Prerequisite: Spring MVC, validation, and testing basics
Log deliberately with SLF4J and Logback: right levels, structured messages, zero sensitive data, and exceptions with full context.
Diagnose failures from logs alone because messages carry context, levels carry meaning, and nothing sensitive leaks.
Prerequisite: Spring Boot fundamentals
Expose safe operational signals and connect logs, metrics, and traces into one production investigation workflow.
Operate a service from symptoms to root cause without exposing sensitive management data.
Prerequisite: Configuration and logging
Use Spring Cache and Redis without turning stale data, stampedes, and unsafe keys into correctness bugs.
Select cacheable reads, design keys and TTLs, and make invalidation observable.
Prerequisite: Spring Data JPA and observability
Move work off the request path while keeping delivery, ordering, retries, and business state observable.
Choose local async work, in-process events, or a broker and state the failure contract of each.
Prerequisite: Application architecture and transactions
Call other systems deliberately: modern HTTP clients with explicit timeouts, bounded retries and circuit breakers, and verified inbound webhooks.
Integrate a third-party API whose failures do not cascade into your own outage.
Prerequisite: Spring MVC and failure-handling basics
Accept uploads without risking memory or security, validate what users send, and store files durably behind controlled access.
Ship an upload feature that bounds memory, blocks malicious files, and keeps private files private.
Prerequisite: Spring MVC, validation, and security
Measure real bottlenecks, tune the hottest paths, and scale Spring Boot services horizontally with evidence instead of folklore.
Turn performance work into measurement-driven scaling decisions backed by load-test evidence.
Prerequisite: Data access, caching, and observability
Package one immutable artifact, inject environment configuration safely, and deploy it with health-aware automation.
Create a repeatable container delivery path with safe startup, rollout, shutdown, and rollback behavior.
Prerequisite: Configuration, testing, and Actuator
Organize boundaries, recognize framework-powered patterns, master proxies and post-processors, and assemble a production-grade capstone.
Defend an architecture through dependency direction, failure behavior, performance evidence, and evolutionary cost.
Prerequisite: Core Spring, transactions, and testing
Split services only around owned capabilities, then design discovery, routing, resilience, communication, and tracing for partial failure.
Design a service boundary and explain how it behaves when dependencies are slow, unavailable, or duplicated.
Prerequisite: API integration, messaging, observability, and deployment
A 70–75 character reading column, descriptive headings, calmer typography, lesson drawers, and an optional focus mode.
Annotated code, bean and request lifecycles, deliberate failures, and evidence-led debugging replace annotation lists.
Retrieval checkpoints, concise model answers, follow-up questions, pitfalls, and module assessments appear throughout the path.
Optional specializations
These topics remain available without making every learner treat distributed systems and specialist infrastructure as prerequisites.
Interview preparation
Use module assessments after the retrieval questions, debugging exercises, and project checkpoints inside each stage.
Reference
Lessons explain the model; official documentation remains the versioned source of truth.