Overview
Syllabus
Intro
What if we designed computer systems for worst case scenarios?
Designing for the worst case often penalizes the average case
Distributed Systems Matter
Networks make design hard
Handling Worst-Case Net Behavior availability addresses delays, drops
DISTRIBUTED TRANSACTIONS (EC2)
But wait! What about CAP?!?!
"Worst" is a Design Tool Example: Coordination-Avoiding Databases
Simple Example: Read Committed
Punchline: Distributed Systems & Networks
Fail-over helps (Dev)Ops
Tail Latency in (Micro)services
Universal Design
This talk: When can designing for the worst case improve the average case?
Reasoning about worst-case scenarios can be a powerful design tool
Taught by
Strange Loop Conference