[LRUG] Final lineup & registration details for February

[Glenn Gillen]

> A: respond quickly by putting the external API call to backgroundjob, and check the response via ajax periodically (could use commet or websocket alternatively).

+1

> B: separate this long running request to different component (eg: node.js on heroku or other PAAS) and call this via cross domain ajax call.

You can't sign up for a node.js account on Heroku any more :(

> C: Don't use Heroku. Heroku is not meant for that kind of purpose.

That's an option. But you're going to have a similar problem wherever you take an app like this. If you're sticking with a ruby stack, I'd opt for option A). If you're keeping it on Heroku, then you'd need to pay for a worker to pick-up the jobs. While I don't know the exact figures, I suspect that if you tried to fix it by increasing the number of dynos to hide the latency from concurrent users you'd need to scale dynos up quicker than you'd have to scale workers.

It's still early days, but I think this library is looking promising for doing job management in a simple and sensible fashion:
https://github.com/ryandotsmith/Queue-Classic

Glen



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20110208/8d484b24/attachment-0003.html>