Resilience Engineering for Spring Services
KRW 620,000 · informational list price
Harden services with timeouts, bulkheads, and graceful degradation paths you can explain.
You instrument thread pools, configure circuit breakers with intentional thresholds, and practice failure drills that respect operator attention. The goal is calm operations, not noisy dashboards.
What you build and study
- Timeout budgets per dependency
- Bulkhead sizing with measurement
- Retry policies with jitter rationale
- Chaos drills scoped to staging
- Operator checklists for partial outages
- Synthetic probes without brittle assertions
- Post-incident writeups with blameless tone
Outcomes
- Tune a sample service using measured latencies
- Draft an operator-facing runbook page
- Run a scoped chaos exercise with cohort peers
Mentor
Hana Seo
Former platform engineer; focuses on readable service boundaries.
Questions
Mentioned briefly; exercises use local fault injection first.
No, but you should be comfortable reading logs and metrics.
Yes, for cohort review; external sharing is not allowed.
Recent reflections
-
“Jitter discussion finally stopped our thundering herd retries.”
-
“Some modules overlap with the microservices walkthrough; pick one if time-bound.”