One of Heroku's employees has a fork of delayed_job that handles autoscaling workers in the background. I use it in conjunction with several hourly cron jobs and it works like a charm. http://github.com/pedro/delayed_job/tree/autoscaling
Yes, I was aware of this, though I haven't had the need to use it yet.
But my question stands: why isn't this stuff very visible - i.e., on Heroku's DJ doc page: http://docs.heroku.com/delayed-job , or at least linked from there? Or published as an official piece of code on the Heroku github page?
Really? I would certainly hope that's not the case. Relying on customers overspending due to technical deficiency seems like a pretty poor business model.
I'd certainly be happier paying more per pro-rated unit of time that I actually use than I am feeling as though I'm in an arms race to not be fleeced.
Is there really that much revenue to skim off the top? Either way, they're paying Amazon out of those charges.
But I'm not so cynical as to think that their success is reliant on this income.
Either way, they're paying Amazon out of those charges.
I'd be extremely surprised if Heroku actually spools up EC2 instances the moment you move the slider. It'd be a far more intelligent (and profitable) design to simply make sure there are sufficient resources to maintain the desired service levels with a buffer to deal with spikes in demand.
It should be relatively straightforward to provide service levels that are functionally identical to actually starting each "dyno" or "worker" with a greatly reduced cost structure.
Relying on customers overspending due to technical deficiency seems like a pretty poor business model.
I didn't mean to say they're relying on it, simply that it's adding to the bottom line and it would be greatly missed.
