Centrifugo VS Benthos

Take a look at Centrifugo - https://centrifugal.dev/ - it provides a way to build efficient real-time messaging system using standard Django without ASGI involved. Source: 11 months ago

Hello, I am an author of Centrifugo project (https://centrifugal.dev/). It's a WebSocket server which scales using Redis. Instead of the approach you described when every message is delivered to every server Centrifugo uses PUB/SUB in a way that every server subscribed only to channels which current server connections have. It should scale pretty well, and resubscribe to channels is super-efficient. All the load... Source: over 1 year ago

Hello, I am author of Centrifugo (https://centrifugal.dev/) project - WebSocket server which scales with Redis. We have several blog posts which may help to answer your questions and give you some real world numbers about using Redis for WebSocket apps. Some links:. Source: over 1 year ago

Https://centrifugal.dev/ It's go native you can even write your own using it's underlying centrifuge library. We use it currently in Production just the docker container to be honest is what we deploy and just use a small config file or flags. Source: over 1 year ago

Hey folks! Centrifugo is an open-source scalable real-time messaging server written in Go language. It's 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. Including NodeJS-based backend which is relevant to this subreddit. And while Javascript/Node ecosystem has good WebSocket tools, I... Source: almost 2 years ago

If you're interested in Golang and data streaming, https://benthos.dev is a good project to contribute to. There are quite a few issues open on the GitHub project which anyone can pick up. Writing new connectors and adding tests / docs is always a good place to start. The maintainer is super-friendly and he's always active on the https://benthos.dev/community channels. I'm also there most of the time, since I've... - Source: Hacker News / about 2 months ago

I have been working in the stream processing space since 2020 and I used Benthos. Since Benthos is a stateless stream processor, I have other components around it which deal with various types of application state, such as Kafka, NATS, Redis, various flavours of SQL databases, MongoDB etc. Source: about 1 year ago

You might want to add Benthos to your stack. It’s Open Source and it works great for data streaming tasks. You could have your task orchestrator (Airflow, Flyte etc) run it on demand. I demoed it at KnativeCon last year. Source: about 1 year ago

A few years ago, I found Benthos (the Open Source data streaming processor) and it was really easy to dive into it and add new features. Going through the various 3rd party libraries that it includes is usually straightforward and I'm comfortable enough with the language and various design patterns now to quickly get what's going on. That was rarely the case with C++. Source: about 1 year ago

This is a miniature OAuth provider implemented in Benthos and Bloblang. It is designed to serve a single OAuth client app and will generate JWT access tokens with limited lifetime. Source: about 1 year ago