ddev VS Centrifugo

Do you already want to try the new version, which is currently in alpha state? With DDEV this is super simple, just paste one command into the terminal.

For development, I will still prefer to continue with DDEV (a tool that I highly recommend). But the adventure with SQLite was very interesting, it really helped me not to pollute my termux.

I use https://ddev.com for almost all of my web project development, which basically automates all of this. Per-project databases, web containers, plugins, etc, and it’s now using Traefik as its router.

I use it with ddev for local development.

https://ddev.readthedocs.io/

With the right combination of overlapping interests, a lot can get done and incredible things get build. See for example the Drupal book or DDEV--both are extremely active Drupal projects, with lots of community activity, outside of drupal.org.

You can go from 0 to 100 quickly with DDEV or Lando: - https://docs.lando.dev/ - https://ddev.readthedocs.io/

For local: have you tried DDEV? Or Lando? they seem pretty fast to me. https://github.com/drud/ddev

Lando works great with Linux, use DDEV for Mac. Both are Docker-based.

With DDEV you can create Docker PHP + NodeJS environments which run on every operating systems in the same way. These environment configuration can be shared via git which makes open source software DDEV a great and robust choice for team projects.

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