I'll +1 on IronWorker. I used it on my most recent application (slottd.com) for both background processing (sending emails) and scheduled job (call back to a destroy action in 10 minutes). Was very easy.
-Corey On Saturday, December 10, 2011 12:57:36 PM UTC-6, Chad Arimura wrote: > > Hey DJ Angst, > > You can also check out IronWorker <http://www.iron.io> (formerly > SimpleWorker). It provides background processing / task queues as a > service and delivers on demand scalability no matter how few or how many > jobs you want to run. We've got users runnings thousands of jobs in > parallel with no issues. > > The two considerations are that IronWorker does not have access to the > Heroku shared database because they don't allow outside connections, and we > also run outside your Rails stack so you'll need to pass along some config > and models, but we can help you with this if your use-case happens to be > complex. We believe that developers should never have to worry about > complex infrastructure giving you more time to build your apps. > > Check it out: http://www.iron.io. > > Disclosure: I'm one of the co-founders of IronWorker. > > Chad Arimura > Iron.io > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To view this discussion on the web visit https://groups.google.com/d/msg/heroku/-/nXV7mrxSmNkJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
