Scaling a monolith isn't scaling microservices
summary
Claim: the techniques that scale a large Rails monolith are not the same as those that scale microservices. Describes concrete tradeoffs between Resque and Sidekiq (Ruby task queues), message-oriented middleware / AMQP for service-to-service JSON messages, and Kafka as an event log. Gives numbers: Shopify queues tens of thousands of jobs a second and deploys core code ~60 deploys a day. Shows a working Kafka-powered dashboard that visualises >$1B in Black Friday/Cyber Monday sales.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:29Outline
- 9:45Long running jobs - Resque
- 10:55Large collections
- 11:18Interruptible job with automatic resuming
- 13:57Background jobs
- 20:01Keep breaking changes manageable
- 22:11Event-carried state transfer requires order information
- 22:50Event notifications are commutative
- 24:55Message oriented middleware








