Services and Rails: The Shit They Don't Tell You
summary
Yammer extracts pieces of a 300+ model Rails monolith into services, running 20 services in production and some handling over a billion requests a day. Expect concrete pain: double‑dispatch backfills, duplicated data, cache invalidation from ActiveRecord, and rollbacks that are hard. Tools and numbers matter—use Vagrant with Soup Kitchen for dev mirrors, Dropwizard New Relic Ganglia for standardized monitoring, and plan capacity, deploy automation, and cleanup before cutting over.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:34Who is this guy?
- 4:11Reusability
- 8:46Conway's Law
- 9:19The Messaging Team
- 10:01Rails and Core Services Teams
- 11:55Example cross-functional team
- 14:46Put them all behind Rails
- 15:44There are lots of ways to do it
