Software/site reliability of distributed systems
summary
Covers practical reliability engineering for a distributed SMS reminder service: diagnosing static failures (disk, network, CPU, memory) and behavioral failures (latency, freshness, correctness, DDos), choosing monitoring tools and trade-offs for synchronous vs asynchronous queues, and capacity decisions like sharding, clustering, and backup sync/async. Describes moving from reactive to proactive practices including request tracing, injecting reliability into development, and validating fixes via simulations/chaos engineering and FMEA-style fault exercises.
AI-written summary · about
related talks
43mSoftware/site reliability of distributed systems
44mReliability for All of Us
29mPractical distributed systems: Building for the real world with chaos engineering
32mThe culture of Site Reliability Engineering
52mPerformance & Stability Anti patterns
51mDesigning for Failure: Build Resilient Services
30mImproving Reliability w/ Error Budgets & SRE
52mFailure is Always an Option