Microservices & Spring Cloud
One app becomes many, on purpose.
When and how to split a monolith into services - and the Spring Cloud toolkit that makes distributed systems manageable: externalized config, service discovery, an API gateway, resilience, distributed tracing, and event-driven messaging.
Lessons in this stage
- 01
Monolith to Microservices
AdvancedWhat microservices really trade off, when the split is worth it, and why 'start with a monolith' is usually right.
16 min - 02
Externalized Configuration
IntermediateSpring Cloud Config: one central, versioned source of configuration for every service and environment.
14 min - 03
Service Discovery
IntermediateLet services find each other by name through a registry (Eureka) instead of hard-coded hosts, with client-side load balancing.
14 min - 04
The API Gateway
IntermediateSpring Cloud Gateway as the single front door: routing, and cross-cutting concerns like auth and rate limiting in one place.
14 min - 05
Resilience: Circuit Breakers
AdvancedStop one failing service from cascading: circuit breakers, retries, timeouts, and fallbacks with Resilience4j.
16 min - 06
Distributed Tracing & Observability
IntermediateFollow one request across many services with trace IDs, using Micrometer Tracing and OpenTelemetry.
14 min - 07
Event-Driven Microservices
AdvancedConnect services through a broker with Spring Cloud Stream, so they communicate by events, not brittle direct calls.
14 min