Bringing Your Rails Monolith Along As The Business Grows
summary
Claims a Rails monolith scales to ~100 engineers and stays maintainable, supported by 4,500+ commits, ~48 committers, ~62k lines of Ruby and ~61k JS, and 97% test coverage. Tooling includes Brakeman, bundle-audit, custom rubocop rules and Datadog. Migration is pragmatic and incremental: convert slow serializers first and enforce Json API serializer conversion rules on touched controllers, postpone big rewrites, spin up an architecture team late, and regret delaying Ember frontend tests.
AI-written summary · about
chapters (10)
- 0:00Start
- 4:22How Big of a Monolith?
- 5:50Testing The Beast
- 9:07Other Tools
- 10:09Usage of Those Tools
- 11:27Modernizing The Code
- 14:00Case Study: AMS and JSON-API
- 17:26Case Study: Enums
- 21:17Case Study: State Machines
- 22:55Retrospective Results
related talks
43mThe history of a Rails monolith
34m"Taming your Rails monolith"
39mTaming Monoliths Without Microservices
21mTaming Monoliths Without Microservices
26mMonolith-ifying perfectly good microservices
32m2000 engineers, 2 millions lines of code: the history of a Rails monolith
30mMonolith-ifying perfectly good microservices
42mHow Rails fosters a diverse and competitive tech ecosystem in the era of big tech
