High Availability With '503: Unavailable'
Lightningat KubeCon + CloudNativeCon Europe 2025 · on Thursday, 2025-04-03· at 16:45· Level 0 | ICC Auditorium·
summary
Claims that embracing 503s as cheap, retryable failures and building apps with Envoy Istio and gRPC drastically reduces HA complexity while keeping user-facing success metrics. Implementation requires generated client libraries with retries-on-by-default, user experiences that tolerate a few quick retries, and idempotent APIs via per-request IDs plus server-side deduplication — Reboot uses its stateful framework to remember completed operations. Demonstrates fewer buffering components (no Knative queue‑proxy) and reports practical pitfalls and when this model is appropriate.
AI-written summary · about
related talks
35mBuilding resilient applications with Durable Execution
20mUber's Failover Architecture: Reconciling Reliability and Efficiency in Hyperscale...
34mDistributed Systems - What Can Go Wrong and How to Get It Right
32mHow does your application behaves when everything goes wrong?
30mSturdy Clouds Creating Resilient Software Defined Data Centers
16mFrom System TAYE7 to High Availability: What, Why, How?
36mDesigning for failure - architecting fault-tolerant system
30mBuilding Resilient Systems with Stacking
