Question 1

How to scale Centrifugo for high concurrent connections?

Accepted Answer

Centrifugo scales horizontally by using Redis or Nats as a backend. Add more Centrifugo nodes and configure them to share the same Redis instance, as detailed in the scalability documentation for handling thousands of connections.

Question 2

Centrifugo vs Socket.IO: which is better for real-time chat?

Accepted Answer

Centrifugo is better for scalable, production-ready PUB/SUB with built-in features like history and presence, while Socket.IO is simpler for basic real-time with fallbacks. Choose Centrifugo if you need extensive control and scalability.

Question 3

Does Centrifugo support mobile push notifications?

Accepted Answer

No, Centrifugo focuses on real-time connections over supported transports. For push notifications, you must integrate with external services like Firebase Cloud Messaging or Apple Push Notification Service.

Question 4

How to handle authentication in Centrifugo with JWT?

Accepted Answer

Centrifugo supports JWT tokens generated by your backend. Configure Centrifugo to validate these tokens, and use the token claims for user identification and channel permissions, as explained in the authentication docs.

Question 5

Can Centrifugo be used with serverless backends?

Accepted Answer

Yes, Centrifugo's HTTP and GRPC APIs allow integration with serverless functions. However, the Centrifugo server itself requires persistent infrastructure, so it's not fully serverless.

Question 6

What are the performance benchmarks for Centrifugo?

Accepted Answer

The documentation and blog provide benchmarks showing high concurrency and low latency with Redis. For specific metrics, refer to the official performance testing resources, which highlight scalability under load.

Centrifugo

What is Centrifugo?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions