Taming Monoliths Without Microservices

on YouTube ↗39m

" summary

A company of ~100 engineers runs a 13‑year Rails monolith with ~700 models and moves about $1B/month; the concrete claim is that careful internal boundaries make microservices optional and safer to adopt. Teams build thin adapters that send value objects instead of ActiveRecord across domains, introduce service objects and avoid callbacks, and experiment to make ActiveRecord private in modules. A slow, measured migration (200 PRs in eight weeks to reach one twelfth of a goal) proves the approach works.

AI-written summary · about

" chapters (13)

1. 0:00Introduction
2. 7:12Presentation Structure
3. 11:29Breaking Model
4. 16:48The swamp
5. 21:59Conceptual compression
6. 23:49Avoid circular dependencies
7. 25:39Use value objects
8. 27:32Private module
9. 28:06Avoid callbacks
10. 29:51Service objects
11. 31:16Move slowly
12. 32:10Make the change easy
13. 33:37Questions

" related talks

• 21mTaming Monoliths Without MicroservicesKelly Sutton · RubyConf AU 2019
• 34m"Taming your Rails monolith"Mugurel Chirica · RubyC 2019
• 26mMonolith-ifying perfectly good microservicesBrian Scanlan · LDX3 London 2025
• 28mBringing Your Rails Monolith Along As The Business GrowsCarrick Rogers · RailsConf 2022
• 30mMonolith-ifying perfectly good microservicesBrian Scalan · Rails World 2023
• 27mScaling a Rails Monolith w/Event Driven MicroservicesMarko Anastasov · WindyCityRails 2016
• 40mMonoliths Between MicroservicesVladimir Dementyev · RailsConf 2020 CE
• 43mThe history of a Rails monolithC.Planas, A. Mikhaylov · rubyday 2024