Centrifugo VS InfluxDB

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:

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

Every time I read criticism of WebSockets it reminds me about WebSuckets (https://speakerdeck.com/3rdeden/websuckets) presentation :)

I am the author of Centrifugo server (https://github.com/centrifugal/centrifugo) - where the main protocol is WebSocket. Agree with many points in post – and if there is a chance to build sth without replacing stateless HTTP to persistent WebSocket (or EventSource, HTTP-streaming, raw TCP etc) – then definitely better to go without persistent connections.

But there are many tasks where WebSockets simply shine – by providing a better UX, providing a more interactive content, instant information/feedback. This is important to keep - even if underlying stack is complicated enough. Not every system need to scale to many machines (ex. multiplayer games with limited number of players), corporate apps not really struggle from massive reconnect scenarios, and so on. So WebSockets are definitely fine for certain scenarios IMO.

I described some problems with WebSockets Centrifugo solves in this blog post - https://centrifugal.dev/blog/2020/11/12/scaling-websocket. I don't want to say there are no problems, I want to say that WebSockets are fine in general and we can do some things to deal with things mentioned in the OP's post.

Install Centrifugo - https://github.com/centrifugal/centrifugo

For those who looking into Laravel WebSockets replacement give a chance to https://github.com/centrifugal/centrifugo - it proved to help a lot dealing with WebSocket connections to backends built in languages without native/performant concurrency support. So you can continue writing business logic in Laravel, but let Centrifugo deal with persistent connection management and issue real-time updates over API.

Scalable Realtime Datastore: The piece examines a scalable datastore specifically created for metrics events and real-time analytics. (2013-09-26, shares: 26787.0)

How does one upgrade from v2 beta to the latest v2? The docs for doing that seem to no longer exist https://github.com/influxdata/influxdb/issues/24393

And InfluxDB Github commit history histogram is telling its story https://github.com/influxdata/influxdb/graphs/contributors

We have 40+ InfluxDB servers (for iot sensor data) but I think in couple of years we will move to TimescaleDB. InfluxDB problem is their company InfluxData that has pivoted away from InfluxDB after v2 release and tried their Rust thing (IOx) and now is promoting their Telegraf. For me this is a sign of no clear vision from company. I can not trust my database to company that will probably abandon InfluxDB in couple of year. Just look commit histogram https://github.com/influxdata/influxdb/graphs/contributors After their released InfluxDB is run on skeleton crew. Also see https://news.ycombinator.com/item?id=23906592

InfluxDB