[LRUG] Queuing systems

[Stevie Graham]

I can appreciate the advantages that Erlang might have over Ruby with its distributed and highly concurrent orientation, but I can't say the same about Node. Node is fast but so are some Ruby VMs, n.b. the excellent work Charles Nutter has been doing recently with JRuby and InvokeDynamic.

Also there are practical things to consider when choosing an ostensibly more suitable language:

- Your team are experts in the adequate language Foo but have zero experience with the more suitable yet radically different language Bar. You're making delivery more difficult than necessary by asking your team to learn a new language as they go. The code probably will not be the greatest and some of your team will be unhappy with the choice for various reasons.
- The full benefit of choosing a different language or paradigm is unlikely to be extracted unless the team fully understands it. This takes time. See previous point.
- Difficulty in recruiting experienced talent in less popular languages.
- Libraries

Sidebar: This thread is great. Very interesting.

S

Stevie Graham (@stevegraham)
Developer Evangelist
Twilio, Inc




On 8 Sep 2011, at 06:18, George Ornbo wrote:

> 
> On Sep 7, 2011 10:14 AM, "Neil Middleton" <neil.middleton at gmail.com> wrote:
> >
> > Simply put - I've got a requirement to capture a crap load of data from an API and stuff it all into a queue to be processed later on.  We would be receiving hundreds of new items per second, over a sustained period.
> >
> > We're looking at hosting on EngineYard so ideally need to stick with what's available there.
> >
> > We cannot really lose any of the received data before processing.
> >
> > Any ideas
> 
> In terms of technology why Ruby? Isn't this the kind of scenario that is just plain hard to do in Ruby and technologies like Erlang or node.js are better at?
> 
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20110908/5996d2a3/attachment-0003.html>