Home/ Questions/Q 8774435
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T18:34:03+00:00

What ruby concurrency lib/framework should I use for the development of a web based

  • 0

What ruby concurrency lib/framework should I use for the development of a web based chat?

I have read about Eventmachine and Celluloid libraries, and about Sinatra::Synchrony, Cramp, Goliath and Gserver concurrency-ready-servers. If I am getting this right, all these libs or servers implement concurrency using two main different approaches: the reactor pattern (mostly all of them), or the use of multithreading (i.e. gserver, …).

Now if this is all correct, and I hope it is, could someone:

  • correct me if it is not…
  • point out other actively developed libraries or frameworks that I’ve missed ?

The reason I am asking this is that I am trying to build, for learning purposes, a web based chat using ruby on server side. It will interact with client using websockets or Server Side Events, with Jquery or something else.

Also I’ve read about using ruby with a Xmpp server, or pub/sub messaging system (like Faye). If I put one of these in the dish, am I correct if I say if that it all shrinks down to having to worry only about making requests to those servers in a non-blocking way, rather than having to set-up a complete “non-blocking” ruby chat server ?

I know this is a bit convoluted, but I hope it still make sense..
But in case I am going totally the wrong direction about something, can someone please give me at least a general, vague idea of what I need to understand better ?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Funny you should ask. Peter Cooper from Ruby Weekly mentioned (Issue 116 – October 25, 2012) a talk subtitled “Ruby developers need to stop using EventMachine. It’s the wrong direction,” which spawned some interesting debate on HN, since many frameworks are built on top of it (Goliath, Cramp, etc.)

    The disenchanted flock either to Celluloid (with Sidekiq as its most famous client), to the Node.js platform or to other languages that offer solid concurrency primitives from the get go. Yes, Go, Erlang, Clojure…

    Personally, I implemented a realtime web-based chat not long ago using Cramp, Redis Pub/Sub and Websockets, loosely adapted from the following demo code. It worked as advertised, but the traffic it gets doesn’t compare to the requirements of some high volume systems elsewhere.

    • 0