advanced · cohort
Microservice Boundaries with Spring Cloud
Service discovery, resilient clients, and gateway policies with a skeptical eye toward sprawl.
7 weeks · 9h/week
JPY 176,000
Informational rate—final fees appear on your enrollment agreement.
Request information Money-back policyProgram narrative
Microservices week balances hype with restraint. You will configure Spring Cloud Gateway routes, implement circuit breakers with explicit fallback semantics, and document when *not* to split a service. Case studies reference JP retail integrations and batch windows.
What ships in the box
- Gateway route lab with weighted blue/green discussion
- Resilience4j configuration matrices
- Distributed tracing with OpenTelemetry wiring sketch
- Saga versus outbox decision worksheet
- Service template repo you can fork
- Cost conversation worksheet for observability stacks
- Mentor critique of your proposed service split
Outcomes you can describe
- Draft a gateway policy table stakeholders can skim
- Demonstrate a circuit breaker with measurable fallback
- List operational costs of an additional service before you build it
Lead mentor
Jonas Weber
Backend mentor; built payment adapters across EU and JP regions.
Cohort questions
We reference deployments but do not teach cluster administration.
Conceptual compare only; no Istio labs.
If your org should stay modular monolith, we will tell you during office hours.
Experience notes
Cost worksheet stopped us from spinning up a twelfth service “just in case.”