Preface
Your website has just crashed, and you’re losing money. The application is built on Rails, runs on MRI, and is served up with Unicorn and Apache. Having this kind of infrastructure means you’re managing more processes than you can count on two hands.
The background jobs are run with Resque,[1] the scheduled jobs are run with cron, and the long-running jobs use Ruby daemons,[2] which are monitored by monit because they tend to crash.[3] It’s going to take some time to figure out which component is the culprit because you have no centralized management interface. Standing up a new server will take almost as long because the infrastructure is so complex. But the website has to get back online if you’re going to stay in business.
The ...
Get Deploying with JRuby 9k now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
