Bowerbirds of Technology: Architecture and Teams at Less-than-Google Scale
summary
Compares decisions at Facebook Google Amazon Uber to practical tradeoffs for smaller teams, pulling concrete cases: Uber’s append-only sparse three-dimensional hash map built on MySQL trades immediate reads, joins, and developer familiarity for linear write scale; Amazon’s enforced SOA spawns service discovery and pager complexity; Instagram stays a Django monolith; Twilio-style RDBMS handles ~20k messages/sec; Google goes from 50M pages per month to one minute over years. Recommends measurable SLOs, sane on-call, public incident doc transparency, and pick mature libraries and vendors.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:25WHAT ARE GOOGLE'S PROBLEMS?
- 13:01BE A PICKY BIRD
- 16:11BUY VS BUILD
- 17:05RELATIONSHIPS
- 20:10THREE NINES
related talks
29mBowerbirds of Technology: Architecture and Operations at Less-Than-Facebook Scale
38mThe Dark Side of Scale
01h 00mService Oriented Architecture for Robust & Scalable Systems
47mPlatform Team Structures and Concerns
18mAPIs at Scale Through Minimalism in Code and Architecture
27mTradeoffs on the road to Observability
01h 02mTools for simplified large scale systems
46mBeyond agile Behind the scenes of the Tech giant unicorns