Winning as a Start-Up by Failing Fast
summary
Claim: scalability is a rich man's problem so start-ups prioritize rapid experiments and pivoting over early clustering. Shows concrete tooling: RiakKV for later scale, Amnesia as a local no‑SQL, and a data abstraction layer to swap stores without rewriting. Uses BEAM fault‑tolerance and supervisors to isolate failures, cites Draw Something switching tech as a real turnaround, and recommends protocols, small process boundaries, and metrics so experiments fail fast but useful. Also names the pattern no sequel flexibility.
AI-written summary · about
chapters (25)
- 0:00Intro
- 2:05Curve
- 3:55Embrace Failure
- 7:05Development Speed
- 12:32Data Models
- 12:47No Sequel
- 13:32Schemas
- 14:52Data abstraction layer
- 16:12Share nothing
- 16:47Failures
- 19:22Bruce Willis
- 20:52Embrace the Failure
- 22:47Fire the Manager
- 23:47Business Benefits
- 25:07Be Gentle
- 26:42Warning
- 27:32Protocols
- 28:37Communication Diagrams
- 29:32Example Board Game
- 31:32Simplifying Code
- 32:32Putting It All Together
- 33:32Architecture
- 34:27Embrace failures
- 37:27Metrics
- 40:47Message By Message
