Stop Building Services, Episode 1: The Phantom Menace
summary
Argues that extracting services often increases fragility rather than reducing it, showing concrete failures: identity service creates two single points of failure and more network calls, extracting a voting feature connected two DBs and then shared a gem so both apps depend on the same bad model, and using Scientist to run old and new code paths in production enables safe rewrites. Recommends untangle code first, group things that change together, and minimize catastrophic failure points.
AI-written summary · about
chapters (24)
- 0:00Intro
- 2:29ServiceOriented Architecture
- 3:16Monoliths
- 12:53Project Goals
- 15:08Drawing the Wrong Lines
- 16:46Improving the Code
- 17:14Scientists
- 18:41Second Case Study
- 20:20Architecture Goals
- 22:16Scaling
- 24:20Overview
- 25:59Architecture Standards
- 27:15Case Study 3
- 28:20Case Study 3 Solution
- 29:58What Went Wrong
- 32:10Alternatives
- 32:58Monolithic Apps
- 33:41Fail gracefully
- 34:15Social features
- 34:39Reliability
- 35:57Grumpiness
- 36:42Fault Tolerance
- 37:33Minimize catastrophic failure
- 37:57Code quality
