centrifuge-dart VS Centrifugo

Connect to it using https://github.com/centrifugal/centrifuge-dart or without any connector library using unidirectional transports: https://centrifugal.dev/docs/transports/overview#unidirectional. For authentication you can pass JWT issued by your Django backend or proxy connection attempt to Django backend ( like shown in this post https://centrifugal.dev/blog/2021/11/04/integrating-with-django-building-chat-application )

Yes. There are clients for bidirectional transports (for example, for Dart/Flutter - https://github.com/centrifugal/centrifuge-dart, and for JS/Swift/Java - so React/Angular/Vue covered, and I never heard what Svelte is but if can use JS libraries then things should work just fine). And it's possible to connect without client libraries if you are using unidirectional transports – just use native browser EventSource object, or use code generation and GRPC to connect to unidirectional GRPC.

Hello, I am author of https://github.com/centrifugal/centrifugo. Our users can choose from WebSocket, EventSource, WebTransport (experimental stabilize in the future). WebRTC is out of scope as the main purpose is central server based real-time json/binary messaging, and WebRTC makes things much more complex since it shines for peer-to-peer and rich media communications.

What I'd like to add is that Centrifugo also supports HTTP-streaming – not mentioned by the OP – but this is a transport which has advantages over Eventsource - like possibility to send POST body on initial request from web browser (with SSE you can not), it supports binary, and with Readable Streams browser API it's widely supported by modern browsers.

Another thing I'd like to mention about Centrifugo - it supports bidirectional WebSocket fallbacks with EventSource and HTTP-streaming, and does this without sticky sessions requirement. I guess nobody else have this at this point. See https://centrifugal.dev/blog/2022/07/19/centrifugo-v4-releas.... Which solves one more practical concern. Sticky sessions is an optimization in Centrifugo case, not a requirement.

If you are interested in topic, we also have a post about WebSocket scalability - https://centrifugal.dev/blog/2020/11/12/scaling-websocket - it covers some design decisions made in Centrifugo.

Check out https://github.com/centrifugal/centrifugo - it was initially designed to be a standalone language-agnostic real-time messaging server. So it may be used with Django without radical change in the existing application and using ASGI. It can also provide a much better performance if you care about it.

https://github.com/centrifugal/centrifugo

It's a complete solution, including server, admin panel and client library.

We're an European company and use OVH, Hetzner and others.

Hello! Theoretically you can take a look at https://github.com/centrifugal/centrifugo - which is a standalone self-hosted real-time messaging server. It does not have native support for Laravel and not compatible with Pusher protocol, though integrating with any backend system, including Laravel: see the blog post https://centrifugal.dev/blog/2021/12/14/laravel-multi-room-chat-tutorial, also has some helper packages:

Hello, it's also possible to design an app in a way that its core will be built with Python, but WebSocket part delegated to something external and efficient like https://github.com/centrifugal/centrifugo – the benefit of the approach is that application business logic is completely decoupled from the real-time transport layer. This may lead to a scalable design with graceful degradation. I think this is especially useful when you already have backend built with Django and need to handle millions of concurrent connections.

Centrifugo https://centrifugal.dev/ https://github.com/centrifugal/centrifugo