The Life and Death of a Rails App
summary
A Rails app that starts as a conference demo becomes a product with hundreds of courses, moves off Heroku to self-hosting with hidden payroll and ops costs, and accumulates 103 Ruby repositories for a team never larger than fifty. It faces GDPR surprises from Devise Trackable IPs, security reports routed through HackerOne $1200 bounties, and eventual acquisition followed by shutdown on June 1, 2018. The concrete decisions are operational debt, service-vs-monolith tradeoffs, code bulldozing, and who keeps access to production.
AI-written summary · about
chapters (10)
- 0:00Start
- 5:25Barriers to Entry
- 10:17GitHub made their own support app!
- 17:55Side-project
- 23:58Rails can scale.
- 29:45Are you GDRP- compliant?
- 30:40Who owns user data?
- 31:14Where does the data go when it's over?
- 35:31Ditch Toxic People
- 36:57Accept Mortality
related talks
54mOpening Conference Keynote
28mBreaking Rules to Ship Products: A Beginner's Rails Journey
41mExploring the History of a 12-year-old Rails Application
32mBuilding HUGE Web Apps: Rails at 1,000,000 Lines of Code
32m2000 engineers, 2 millions lines of code: the history of a Rails monolith
20mSafely Decomposing a Highly Available Rails App
27mScaling Ruby Applications: Challenges, Solutions and Best Practices
28mServices and Rails: The Shit They Don't Tell You