AppHarbor background workers are now in beta, announcement here: http://blog.appharbor.com/2012/03/08/background-workers-in-beta
Hmmm..... think its bad business not to answer back on post for over 8 month now..... Have you closed down or...
Is there an update on this? Your blog post saying you are working on it is dated January. So, it's been almost a year...I'd really like to know what's happening since this has implications on my architecture.
https://appharbor.com/page/pricing says background jobs costs $0.05 / hour, does that mean it's possible to use 'em already, cannot find it anywhere?
I definitely like this idea. Being able to trigger them and have them spin up and down as needed would also be interesting.
added my 3 votes on this. do you have a date when we can except this feature to be added to appharbor?
I'm also looking forward the background workers! with message queue like (Amazon SQS) It's one way to acheive the scability and the decoupling.
Definitely need background workers to process messages from queues for async work.
Any update on background jobs or online cron applications?
Was wondering how this was coming along, any updates?
Here's how StackOverflow used to do it (although they don't anymore): http://blog.stackoverflow.com/2008/07/easy-background-tasks-in-aspnet/
It's pretty slick when you are constrained by your host (shared hosting, etc). At the very least, it a temporary workaround until it's baked in to AppHarbor.
Admintt (Admin, AppHarbor) commented
Right now, it is acceptable to create a second application for the purpose, but since this is prohibited in our terms, it will only be permitted until we introduce a proper solution.
Do you have suggestions or guidelines on what to do in the meantime? I have some jobs that can take up to a couple minutes to complete which can cause the web server to stop responding while they're running. Is it ok, to create a second AppHarbor Application just for these jobs? Or would that cause other issues? I can be reached at email@example.com
You guys should base it on TopShelf and the immensely cool "shelving" feature
How about implementing it as simply a URL in the web app that gets pinged at a regular (configurable) interval? You then simply create an action on a "BackgroundJobsController" say (could be IP address restricted, to mitigate DoS), and it's job done.
I'd love something like this. My project relies heavily on webscraping and having a job that can run and update the database is exactly what I need!
This would go great in an SDK. It would probably be an interface that you implement and the AppHarbor stack could find those classes in your assembly and execute it based on some settings in the dashboard. CRON anyone?