I have a Rails webapp [deployed on Heroku] that repeats a series of HTTP calls to other sites using the Heroku rake: cron function. The current situation is not perfect; The rake: cron process runs in a single thread, which means that HTTP calls are made sequentially; which in turn means that between calls to the same site for a long time [usually 2 minutes].
I would like to execute this process in parallel and reduce the time between calls to 10 seconds. When I see Kevin Smith Erlang in Practice, I am selling for the idea of using Erlang as a back-end. What I'm trying to figure out [given the comments of Damien Katz ] is whether I should: a) rewrite the entire webapp to Erlang, front end and all or b) support a split structure using the Rails / Erlang interface.
I like the idea of using a 100% Erlang stack for a project; I need to use some kind of web infrastructure Erlang [Nitrogen? Erlyweb?]; I am worried that they are not mature enough, and I will spend my time on the web part of the project with them.
Any opinion? Thanks.
source
share