websockets - Redis PubSub, NodeJS, and Socket.io

  •        259

Redis PubSub, NodeJS, and Socket.io example



config : ^1.24.0
express : ^4.14.0
redis : ^2.6.3
socket.io : ^1.5.1



Related Projects

scrumblr - Collaborative Online Scrum Tool Using Websockets, Node.js, jQuery, and CSS3

  •    HTML

scrumblr is a web-based simulation of a physical agile kanban board that supports real-time collaboration. it is built using node.js, websockets (using socket.io), CSS3, and jquery. i hope you like it. alternatively, you can follow the instructions below to setup scrumblr yourself. it is very simple -- it just uses redis and node.js.

Soketi - Just another simple, fast, and resilient open-source WebSockets server

  •    Typescript

The soketi server is built on top of uWebSockets.js - a C application ported to Node.js. uWebSockets.js is demonstrated to perform at levels 8.5x that of Fastify and at least 10x that of Socket.IO. It implements the Pusher Protocol v7. Therefore, any Pusher-maintained or compatible client can connect to it, bringing a plug-and-play experience for existing applications that are already compatible with this protocol.

docker-compose-nodejs-examples - Finally some real world examples on getting started with Docker Compose and Nodejs

  •    Javascript

Docker Compose is an awesome tool for creating isolated development environments with Docker by using simple configurations with YAML. It's clean and easy enough to wrap your head around, even if you are new to Docker. Even though, the official website is lacking some practial, real world examples for getting started with Docker Compose and Nodejs. I hope the following real world examples will save you from some headache (like I had) while trying to figure out how to (pragmatically) use Docker Compose for your Nodejs apps.

ember-websockets - EmberJS WebSockets and Socket.IO addon

  •    Javascript

The send method takes 2 arguments. A message which is passed into the native websockets send method and an optional stringify boolean. This boolean, if set to true, will do a JSON.stringify to the message before passing it to the websocket send method. If you are sending strings it is recommended to pass true. socketFor takes two arguments: a url, a protocol array (optional), and returns a socket instance from its cache or a new websocket connection if one was not found.

primus - :zap: Primus, the creator god of the transformers & an abstraction layer for real-time to prevent module lock-in

  •    Javascript

Primus, the creator god of transformers but now also known as universal wrapper for real-time frameworks. There are a lot of real-time frameworks available for Node.js and they all have different opinions on how real-time should be done. Primus provides a common low level interface to communicate in real-time using various real-time frameworks.If you deploy your application behind a reverse proxy (Nginx, HAProxy, etc.) you might need to add WebSocket specific settings to its configuration files. If you intend to use WebSockets, please ensure that these settings have been added. There are some example configuration files available in the observing/balancerbattle repository.

Delivery.js - Asynchronous Bidirectional File Transfers For Node.js via Socket.IO

  •    Javascript

Sending files to the server, and pushing files to the client should be as easy as possible. Delivery.js uses Node.js and Socket.IO to make it easy to push files to the client, or send them to the server. Files can be pushed to the client as text (utf8) or base64 (for images and binary files). delivery.js can be found within lib/client.

nodock - Docker Compose for Node projects with Node, MySQL, Redis, MongoDB, NGINX, Apache2, Memcached, Certbot and RabbitMQ images

  •    Shell

The docker Node.js image is very simple, you give it an entrypoint and it runs it. This is fine for very simple/small scripts but for larger projects you'll probably want something a bit more robust. The goal of NoDock is to provide a complete environment for your node project: Node.js service(s), databases, web servers, queues, etc. while doing the "wiring" for you.

mock-socket - Javascript mocking library for websockets and socket.io

  •    Javascript

To use within a node environment you can simply import or require the files directly. This option is great for phantomjs or CI environments. This project uses mocha as its test framework. Tests are located in /test and have 1 of 3 file name prefixes (functional-, issue-#, or unit-).

django-socketio - WebSockets for Django

  •    Python

django-socketio is currently bound to socket.io 0.6, which is considerably out of date. It's fully functional, but some browsers now have newer implentations of WebSockets, and so alternative socket.io transports are fallen back to in these cases. django-socketio is a BSD licensed Django application that brings together a variety of features that allow you to use WebSockets seamlessly with any Django project.

socket.io-php-emitter - A PHP implementation of socket.io-emitter

  •    PHP

A PHP implementation of socket.io-emitter. This project requires a Redis client for PHP. If you dont have the PECL Redis installed, the emitter will default to using TinyRedisClient. You can, however, pass in any Redis client that supports a publish method.

laravel-blog - Laravel 6

  •    PHP

Now you can access the application via http://localhost:8000. There is no need to run php artisan serve. PHP is already running in a dedicated container.

goatee - A Redis-backed notification server written in Go

  •    Go

A Redis-backed notification server written in Go. ##Usage goatee works by listening on a channel via Redis Pub/Sub and then sending the received message to connected clients via WebSockets. Clients may create channels to listen on by using the goatee client library.

hapi-socketio-redis-chat-example - :speech_balloon: Real-time Chat using Hapi

  •    Elm

Node.js Chat Apps are practically the "Hello World" of real-time apps. If you Google for "node.js chat example" you will see thousands of results! But ... 90% of the examples use Express.js, 95% use MongoDB to store data/messages and 100% have zero tests. So, this example is for the the people who prefer to have examples that are fully explained (including tests). As with all our examples we have a suite of tests.


  •    Javascript

A Real Time Chat Application built using Node.js, Express, Mongoose, Socket.io, Passport, & Redis. Make sure you have Node.js and npm installed.

socket.io + WebSockets


implementation WebSockets for socket.io. programming language is C#


  •    Javascript

By running socket.io with the socket.io-redis adapter you can run multiple socket.io instances in different processes or servers that can all broadcast and emit events to and from each other. will properly be broadcast to the clients through the Redis Pub/Sub mechanism.

redis-cluster - HA Redis Cluster with Sentinel by Docker Compose

  •    Shell

Using Docker Compose to setup a redis cluster with sentinel.

django-websocket-redis - Websockets for Django applications using Redis as message queue

  •    Python

Detailed documentation on ReadTheDocs. This module implements websockets on top of Django without requiring any additional framework. For messaging it uses the Redis datastore and in a production environment, it is intended to work under uWSGI and behind NGiNX or Apache version 2.4.5 or later.

uWebSockets.js - μWebSockets for Node.js back-ends

  •    C++

µWebSockets.js is an HTTP/WebSocket server for Node.js that runs 8.5x that of Fastify and at least 10x that of Socket.IO. It comes with both router and pub/sub support and is suited for extraordinary performance needs. Being written in native code directly targeting the Linux kernel makes it way faster than any JavaScript implementation. It powers many of the biggest crypto exchanges in the world, handling trade volumes of multiple billions of USD every day.

redispapa - another redis monitor by using flask, angular, socket.io

  •    Python

we use redis info to monitor the redis usage. PAPA means a father who is monitoring the redis. accoding to the redis doc, it is be recommanded to use info other than monitor.

We have large collection of open source products. Follow the tags from Tag Cloud >>

Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.