Mega Rails

on YouTube ↗31m

" summary

Square describes how a Rails app hits a wall: ~1,000 controllers, billion-row analytics tables, and $30,000 MySQL boxes with Fusion‑IO cards to survive IO. Tests take too long, a single refresh during deploy can bring services down, and mail templates and analytics clog the main app. The solution is concrete: add service interfaces (minimal internal APIs), extract to private gem for reusable libs, then replicate and ETL your data and cut services out into separate deploys.

AI-written summary · about

" chapters (25)

1. 0:00Jack Danger
2. 0:52Square
3. 1:35Mega Rails
4. 5:25Can Rails scale
5. 5:50Scaling problems
6. 6:53Developer headcount
7. 7:13Early days
8. 7:46Analytics
9. 8:09Rails can do anything
10. 8:44Subclass action mailer
11. 9:12Users
12. 10:47Tradeoffs
13. 11:38Examples
14. 11:52Multiple queries
15. 13:01Postgres
16. 15:24User Data
17. 17:47Logging
18. 18:07Data Analysis
19. 19:07Admin Interface
20. 21:02Ownership
21. 23:46Rails
22. 25:25Building a Service Interface
23. 27:17Marketing Frontend
24. 28:34Git Clone
25. 29:22Conclusion

" related talks

• 32mBuilding HUGE Web Apps: Rails at 1,000,000 Lines of CodeBrad Urani · Southeast Ruby 2017
• 33mServices and Rails: The Shit They Don't Tell YouBrian Morton · Ruby on Ales 2013
• 34mIndustrial RailsChristian Weyer · RubyConf Portugal 2015
• 28mServices and Rails: The Shit They Don't Tell YouBrian Morton · Big Ruby 2013
• 37mThe Recipe for the Worlds Largest Rails MonolithAkira Matsuda · Ruby on Ales 2015
• 42mHow Rails fosters a diverse and competitive tech ecosystem in the era of big techJordan Trevino · RailsConf 2023
• 31mA Rails performance guidebook: from 0 to 1B requests/dayCristian Planas · RubyConf TH 2022
• 33mServices and Rails: The Sh*t They Don't Tell YouBrian Morton · RailsConf 2013