Designing Fault-Tolerant Software with Control System Transparency
summary
Argues that four concrete transparencies—transparent objectives, transparent models, transparent knowledge, transparent control—produce robust fault tolerance, citing GN&C Fault Protection fundamentals and the Voyager probes still operating 46 years after 1977 as evidence. Uses DNS TTL, HTTP cache‑control headers, a circuit‑breaker example, and Little’s law (n = x r) to show how models predict behavior. Proposes a stateless microservice control plane* that consumes telemetry, applies simple models, adjusts autoscaling and connection pools, and exposes SLA‑style objectives for predictable automation.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:50Voyager probe fault tolerance
- 5:00States behaviors and models
- 9:15Transparent objectives
- 16:59Transparent models for fault tolerance
- 23:20Little's law basics
- 29:25Transparent knowledge in distributed systems
- 36:19Control decisions and stateless functions
- 40:10Microservice control plane design
- 47:38Summary
related talks
36mDesigning for failure - architecting fault-tolerant system
31mDesigning for failure
43mFault tolerance – look, it’s possible!
30mFast, Available, Catastrophically Failing? Safely Avoiding Behavioral Incidents in Complex Production Systems
55mGoing Resilient
36mFlexible Byzantine Fault Tolerance
29mThe art of being resilient. How to handle failures gracefully in Distributed Systems.
40mSystems Thinking for Developers