FnordMetric is a Ruby Event-Tracking gem on steroids

FnordMetric is a Ruby Event-Tracking gem on steroids

FnordMetric is a Ruby Event-Tracking gem on steroids

A websocket service compatible with Pusher libraries

A websocket service compatible with Pusher libraries

Server-Sent Events via Redis

Firehose is a realtime web application toolkit for building realtime Ruby web applications.

A scalable XMPP chat server.

Redis backend engine for Faye

A WebRTC signaling server implemented with WebSockets, EventMachine and Redis Pub-Sub

Requires an evented Ruby dispatcher, like Thin

webrtc-rails is a gem for easy to create video chat app.

Simple ruby implementation of a Redis Reactor used for publish subscribe communication between celluloid actors using Reel websocket server

Diaspora-vines is a Vines fork build for diaspora integration. DO NOT use it unless you know what you are doing!

EventMachine multiple APNs connections Management Solution. You can use multiple cert and connection to apple's APNs server.

A generic eventmachine library for storing arbitrary objects in buckets with callbacks on threshold reached

em-hiredis with sentinel support for failover

EventMachine pub/sub using Redis list, resilient to failure

Em-resque is a version of Resque, which offers non-blocking and non-forking workers. The idea is to have fast as possible workers for tasks with lots of IO like pinging third party servers or hitting the database. The async worker is using fibers through Synchrony library to reduce the amount of callback functions. There's one fiber for worker and if one of the workers is blocking, it will block all the workers at the same time. The idea to use this version and not the regular Resque is to reduce the amount of SQL connections for high-load services. Using one process for many workers gives a better control to the amount of SQL connections. For using Resque please refer the original project. https://github.com/defunkt/resque/ The library adds two rake tasks over Resque: * resque:work_async for working inside the EventMachine

Allow a long running faye client to reconnect to a faye server with the same client ID