How Rails fosters a diverse and competitive tech ecosystem in the era of big tech
summary
A client with hundreds of millions in funding, ~50–75 engineers, a ~300,000‑line single-page app and about 20 microservices proves the claim that big‑Tech patterns demand far more resourcing: migrations create slow, unpredictable delivery and brittle ops. The rescue rebuild uses a restored Rails monolith with server-rendered front end (TurboLinks + Stimulus), ActiveRecord connecting to multiple databases, and iframed integration via postMessage/penpal. Result: much faster velocity, simpler teams, lower cost, and eventual IPO.
AI-written summary · about
chapters (13)
- 0:00Rails and Phoebus cartel
- 2:50Big Tech patterns harm small firms
- 8:08Computational vs systems thinking
- 10:54Big Tech patterns in media
- 13:21Resourcing constraints and escape
- 17:36Failed microservices migration
- 23:17Rails cost-effective alternative
- 28:54Rebuilding monolith from services
- 32:23Scale and character in Big Tech
- 35:14Digital market power dangers
- 38:23Antitrust and techno-feudalism
- 40:28Rails first practices
- 41:31Conclusion & Q&A
related talks
32mHow I architected my big Rails app for success!
28mBringing Your Rails Monolith Along As The Business Grows
37mArchitecture: The Next Generation
52mKeynote: Startups on Rails in 2024
52mKeynote: Startups on Rails in 2024
34mIndustrial Rails
24mThe Rails Features we Loved, Lost, and Laughed at
37mHow I Architected My Big Rails App For Success