Scale Fail
summary
A satire of scaling advice that lists concrete anti-patterns with examples: choose tech by Reddit buzz (build with Clojure and Qt), avoid performance graphs and monitoring, favor single-threaded code and a single-master queue that serializes every job, remove all caching and send every jQuery user action straight to the master database, and intentionally create overloaded load balancers as single points of failure. Mentions Erlang (Joe Armstrong) as the scalable counterexample and treats these choices as guaranteed to cause dramatic outages.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:511. Be Trendy
- 1:47Let History Be Your Guide
- 2:02Barn Door Troubleshooting
- 2:17Parallel Programming
- 2:47How to Single-Thread Your Code
- 3:02The Old Way: Caching
- 3:17The New Way: Direct2DB
- 3:41Hard to Scale
- 4:17Single Point of Failure
- 4:32Cascading Failure
- 4:47Be Sexy
related talks
48mWeb scale for the rest of us
29mWhen Web Scale Doesn't Make Sense
26mBeat the curve how to stay fast at scale
30mAbove the Clouds: Investigating Systems from 32,000 ft.
41mForget Scaling: Focus on Performance
38mA Practical Look at Performance Theory
35mThe elements of scaling
08mLee Atchison (New Relic)