Services and Rails: The Shit They Don't Tell You
summary
A clear playbook emerges: a 300+ model, 200 controller Rails monolith backed by 20+ JVM services and some endpoints doing over a billion requests a day turns into operational pain and requires iterative extraction, tooling, and org change. Expect surprises like a 98% cache hit rate that makes direct DB writes disastrous, messy double-dispatch backfill to migrate data, and the need for local reproducibility with vagrant plus internal tools like soup kitchen and one‑click deploy, Dropwizard, and record_cache for monitoring and stability.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:43Why Build Services
- 5:39Loose Coupling
- 10:24Rails Team
- 10:56Cross-Functional Teams
- 21:42Monitoring and Alerting
- 24:44Recap
- 26:43Be Ready To Be Wrong
related talks
33mServices and Rails: The Shit They Don't Tell You
33mServices and Rails: The Sh*t They Don't Tell You
40mService Architectures for Mere Mortals
31mMega Rails
41mOff the Tracks - Challenging the Rails Mindset
31mA Rails performance guidebook: from 0 to 1B requests/day
22mNitty Gritty Service Building
28mNitty Gritty Service Building