Serverless Workers & Containers
Pattern: Creating Task-Level Workers at Runtime
Overview A type of topic appearing more and more frequently in StackOverflow and Quora are questions on general architecture and app design. We came across one the other day on approaches to queuing and scheduling workers. A good worker pattern – based on what we’ve seen and done – is to chunk the work (and…
Read MoreWhy IronWorker is Better than Heroku Workers / Delayed Job
Overview First off, I would like to say that we use and love Heroku, the system they’ve built is game-changing and 100% awesome, but their worker system is limited and does not meet our needs. Here are the top 4 reasons why IronWorker is better than Heroku’s worker system and Delayed Job (Heroku’s system is…
Read MoreWorker Queues as a Key Variable
Anyone working on a serious web app knows that a worker queue makes up a key component within the app architecture. So important is it that the infrastructure equation is typically broken into servers, workers, and datastores. Sure, there are other components and line items (cdn, bandwidth, etc) that an app can’t do within, but…
Read MoreThe Ruby Compute Cloud
One of the main uses of SimpleWorker is as a worker queue for running background jobs within a web application. A second use — and one that marks a big shift in the cloud — is that of a Ruby Compute Cloud.
Read MoreSimpleWorker Usage Pattern Graph
SimpleWorker is a job queuing and scheduling system so while a lot of work comes in at random times usually based on some event in their system (ie: a user clicks a button), there are a lot of scheduled jobs too and those scheduled jobs have a huge affect on the capacity requirements for SimpleWorker.…
Read MoreIncluding other files in your Worker with “merge”
Previously, your worker file/class had to be self contained (ie: single file including all code for the worker). Now you can use the new “merge” class method for instance: class TestWorker2 < SimpleWorker::Base merge “models/model_1.rb”
Read More