Convert Figma logo to code with AI

centrifugal logocentrifugo

Scalable real-time messaging server in a language-agnostic way. Self-hosted alternative to Pubnub, Pusher, Ably. Set up once and forever.

8,277
585
8,277
24

Top Related Projects

33,019

⚡️ Express inspired web framework written in Go

6,094

Tiny WebSocket library for Go.

Quick Overview

Centrifugo is a scalable real-time messaging server written in Go. It provides a way to add real-time features to your web, mobile, and server-side applications using various protocols such as WebSocket, HTTP-streaming, SSE, GRPC, and more. Centrifugo supports both pub/sub and uni-directional messaging patterns.

Pros

  • Highly scalable and performant, capable of handling millions of simultaneous connections
  • Supports multiple protocols and client libraries for various programming languages
  • Provides built-in authentication and channel authorization mechanisms
  • Offers features like presence, join/leave events, and message history

Cons

  • Requires separate setup and maintenance of an additional server component
  • Learning curve for developers new to real-time messaging concepts
  • Limited built-in persistence options for message history
  • May require additional configuration for complex deployment scenarios

Code Examples

  1. Connecting to Centrifugo using JavaScript client:
import Centrifuge from 'centrifuge';

const centrifuge = new Centrifuge('ws://localhost:8000/connection/websocket');
centrifuge.connect();

centrifuge.on('connect', function(ctx) {
    console.log("Connected:", ctx);
});
  1. Publishing a message to a channel:
const channel = centrifuge.newSubscription("news");
channel.publish({ text: "Hello, World!" })
    .then(function(res) {
        console.log("Publication success", res);
    }, function(err) {
        console.error("Publication error", err);
    });
  1. Subscribing to a channel and handling incoming messages:
const channel = centrifuge.newSubscription("news");
channel.on('publication', function(message) {
    console.log("Received message:", message);
});
channel.subscribe();

Getting Started

  1. Install Centrifugo:

    wget https://github.com/centrifugal/centrifugo/releases/download/v4.1.2/centrifugo_4.1.2_linux_amd64.tar.gz
    tar xvfz centrifugo_4.1.2_linux_amd64.tar.gz
    
  2. Create a configuration file config.json:

    {
      "token_hmac_secret_key": "your-secret-key",
      "api_key": "your-api-key",
      "allow_subscribe_for_client": true
    }
    
  3. Run Centrifugo:

    ./centrifugo --config=config.json
    
  4. Install and use a client library (e.g., JavaScript):

    npm install centrifuge
    

    Then use the code examples provided above to connect and interact with Centrifugo.

Competitor Comparisons

33,019

⚡️ Express inspired web framework written in Go

Pros of Fiber

  • Extremely fast and lightweight web framework
  • Express-inspired API, making it easy for Node.js developers to transition
  • Extensive middleware ecosystem and built-in features

Cons of Fiber

  • Less mature compared to Centrifugo, which has been around longer
  • Focused on HTTP routing, lacking real-time capabilities out of the box
  • Smaller community and fewer production-level deployments

Code Comparison

Fiber (HTTP routing):

app := fiber.New()
app.Get("/", func(c *fiber.Ctx) error {
    return c.SendString("Hello, World!")
})
app.Listen(":3000")

Centrifugo (WebSocket handling):

config := centrifuge.DefaultConfig
node, _ := centrifuge.New(config)
node.OnConnect(func(client *centrifuge.Client) {
    // Handle new connection
})

While both are Go-based, Fiber is primarily an HTTP routing framework, whereas Centrifugo is specialized for real-time messaging and WebSocket communication. Fiber offers a more familiar API for web developers, while Centrifugo provides robust real-time features out of the box. The choice between them depends on the specific requirements of your project, with Fiber being more suitable for traditional web applications and Centrifugo excelling in real-time communication scenarios.

6,094

Tiny WebSocket library for Go.

Pros of ws

  • Lightweight and focused WebSocket implementation
  • Low-level control and flexibility for custom WebSocket applications
  • Highly performant with minimal overhead

Cons of ws

  • Requires more manual implementation for advanced features
  • Less out-of-the-box functionality compared to Centrifugo
  • Steeper learning curve for complex real-time applications

Code Comparison

ws:

conn, _, _, err := ws.DefaultDialer.Dial(ctx, "ws://example.com")
if err != nil {
    // Handle error
}
defer conn.Close()

Centrifugo (client-side JavaScript):

const centrifuge = new Centrifuge('ws://example.com/connection/websocket');
centrifuge.subscribe("channel", function(message) {
    console.log(message);
});
centrifuge.connect();

Summary

ws is a low-level WebSocket library offering high performance and flexibility, ideal for custom implementations. Centrifugo provides a more comprehensive real-time messaging solution with built-in features like pub/sub and presence. ws is better suited for developers who need fine-grained control, while Centrifugo offers a higher-level abstraction for rapid development of real-time applications.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

Centrifugo is an open-source scalable real-time messaging server. Centrifugo can instantly deliver messages to application online users connected over supported transports (WebSocket, HTTP-streaming, SSE/EventSource, GRPC, WebTransport). Centrifugo has the concept of channel subscriptions – so it's a user-facing PUB/SUB server.

Centrifugo is language-agnostic and can be used to build chat apps, live comments, multiplayer games, real-time data visualizations, collaborative tools, etc. in combination with any backend. It is well suited for modern architectures and allows decoupling the business logic from the real-time transport layer.

Several official client SDKs for browser and mobile development wrap the bidirectional protocol. In addition, Centrifugo supports a unidirectional approach for simple use cases with no SDK dependency.

Documentation

Join community

Why Centrifugo

The core idea of Centrifugo is simple – it's a PUB/SUB server on top of modern real-time transports:

The hard part is to make this concept production-ready, efficient, flexible and available from different application environments. Centrifugo is a mature solution that already helped many projects with adding real-time features and scale towards many concurrent connections. Centrifugo provides a set of features not available in other open-source solutions in the area:

  • Efficient real-time transports: WebSocket, HTTP-streaming, Server-Sent Events (SSE), GRPC, WebTransport
  • Built-in scalability with Redis (or Redis Cluster, or Redis-compatible storage – ex. AWS Elasticache, KeyDB, DragonflyDB, etc), or Nats.
  • Simple HTTP and GRPC server API to communicate with Centrifugo from the app backend
  • Flexible connection authentication mechanisms: JWT and proxy-like
  • Channel subscription multiplexing over a single connection
  • Different types of subscriptions: client-side and server-side
  • Various channel permission strategies, channel namespace concept
  • Hot message history in channels, with automatic message recovery upon reconnect, cache recovery mode (deliver latest publication immediately upon subscription)
  • Delta compression in channels based on Fossil algorithm
  • Online channel presence information, with join/leave notifications
  • A way to send RPC calls to the backend over the real-time connection
  • Strict and effective client protocol wrapped by several official SDKs
  • JSON and binary Protobuf message transfer, with optimized serialization
  • Beautiful embedded admin web UI
  • And much more, visit Centrifugo documentation site

Backing

This repository is hosted by packagecloud.io.

Private NPM registry and Maven, RPM, DEB, PyPi and RubyGem Repository · packagecloud

Also thanks to JetBrains for supporting OSS (most of the code here written in Goland):

JetBrains logo

NPM DownloadsLast 30 Days