4 ms·
What would be the advantage of using this vs using Resque + S3 + heroku worker auto-scaling?
by jblake 14y ago
What would be the advantage of using this vs using Resque + S3 + heroku worker auto-scaling?
- scosman 14y agoI've set up this exact flow using delayed_job, heroku, S3 and paperclip (an awesome gem wrapping imagemagick). I'm with jblake, I don't see the advantage.
- nico_h 14y agoPresumably: cheaper, easier set up. Sounds a lot like PiCloud.com
- jblake 14y agoThe way I understand their pricing (.05/hr, .10/hr, .15/hr based on minutes jobs get pulled off queue), I'm essentially paying 3x more for priority queuing that I can bypass by setting the INTERVAL=3 in Resque. Hm. This an expensive way to set a variable.
- treeder 14y agoIronWorker is billed by the second so if an image takes 5 seconds to process, you only get billed for 5 seconds of the hour. No need to deal with auto-scaling heroku workers to keep your costs down. And priority on IronWorker has a much different meaning than setting it on your own private Resque instance so comparing that based on price isn't really a fair comparison.
- treeder 14y agoNo resque setup/management, no auto-scaling setup, scale huge with zero effort (go from processing one image to millions without lifting a finger), redundancy and reliability (how are you going to ensure that with your Resque?), full visibility into your tasks, etc.