INTERMEDIATE · 8 MODULES · 64 LESSONS
Resilience and Reliability Patterns
Keep your system standing when one of its parts fails, with timeouts, retries, idempotency, circuit breakers, and graceful degradation, measured before and after.
- For you if
- Your service depends on APIs or services that sometimes fail or slow down.
- By the end
- You'll know when to retry and when not to, how to avoid double charges, and how to stop a cascading failure.
- You need
- Basic Python and a service you've built that calls another API. Everything is simulated in Python.

Curriculum
01Por qué fallan los sistemas distribuidos
- Module introduction: the day `shipping` took down the whole checkout
- Partial failure: in distributed systems, something is always broken
- The fallacies of distributed computing
- Cascading failure: how a slow dependency takes everything down
- Pool exhaustion: why a slow `shipping` exhausts `orders`' threads
- Why the monolith didn't have this problem
- The map of Mercado's checkout failure points
- Mini-project: map the failure modes of Mercado's checkout
04Idempotencia
05Circuit breakers
- Module introduction: stop hitting a dead one
- The cost of keeping calling a dead one, measured
- The three states of the circuit breaker
- From CLOSED to OPEN: opening by threshold
- HALF_OPEN and automatic recovery
- Circuit breaker vs. retry: insisting vs. giving up
- Choosing the threshold and the cooldown
- Project: put a breaker on `shipping` in Mercado and measure
08Proyecto — haz resiliente el checkout de Mercado
Reviews
What students say
These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.
No approved reviews yet.
Be the first to share your experience!