Releases: centrifugal/centrifugo
v5.2.0
Centrifugo is an open-source scalable real-time messaging server. Centrifugo can instantly deliver messages to application online users connected over supported transports (WebSocket, HTTP-streaming, SSE/EventSource, GRPC, SockJS, WebTransport). Centrifugo has the concept of a channel – so it's a user-facing PUB/SUB server.
Centrifugo is 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. It is well suited for modern architectures and allows decoupling the business logic from the real-time transport layer.
Several official client SDKs for browser and mobile development wrap the bidirectional protocol. In addition, Centrifugo supports a unidirectional approach for simple use cases with no SDK dependency.
For details, go to the Centrifugo documentation site.
What's changed
Improvements
- Launching the official tutorial showing the process of building complex real-time application with Centrifugo in detail. It's called Grand Tutorial, and we have a special section on the site for it. In the tutorial we build a WebSocket chat (messenger) app with Django, React and Centrifugo. We cover various aspects of building a production-grade app with Centrifugo and going beyond basics usually shown in instant messaging app tutorials. The idea to keep it in a separate section on the site instead of a blog is to maintain the tutorial actual and extend as time goes.
- Introducing built-in asynchronous consumers. From PostgreSQL outbox table (to natively support transactional outbox) and from Kafka topics. Notably, the "Grand Tutorial" mentioned earlier demonstrates the practical use of both built-in consumers, including the Change Data Capture (CDC) approach for streaming data to Centrifugo using the Debezium connector for PostgreSQL with Kafka Connect.
- Centrifugo now offers the capability to specify an
idempotency_key
when invokingpublish
orbroadcast
server API methods. This is a key Centrifugo will use to prevent duplicate sending of the same publication to a channel. This allows making effective retries when publishing to Centrifugo. Centrifugo maintains a cache of results associated with the used idempotency keys during publishing for a duration of 5 minutes. This cache is utilized to prevent the redundant publication of a message and its addition to the message history if it already exists in the cache. See updated docs for publish and broadcast server APIs. - Refactor
MakeTLSConfig
and support mTLS on server by @tie, see #739. This means mTLS is supported for all TLS configurations in Centrifugo – by using TLS optionstls_client_ca
ortls_client_ca_pem
. - Added possibility to set
parallel
boolean flag in batch API – to make batch commands processing parallel on Centrifugo side, potentially reducing latency, especially when using the Redis engine, as there is no need to wait for N * RTT (Round Trip Time) for sequential command processing.
Misc
- Release is built using Go v1.21.5
- Improvements to the code base by introducing the use of the
Service
interface with aRun(ctx context.Context) error
method. This approach is now recommended for the proper initiation and termination of various extension services within Centrifugo.
v5.1.2
Centrifugo is an open-source scalable real-time messaging server. Centrifugo can instantly deliver messages to application online users connected over supported transports (WebSocket, HTTP-streaming, SSE/EventSource, GRPC, SockJS, WebTransport). Centrifugo has the concept of a channel – so it's a user-facing PUB/SUB server.
Centrifugo is 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. It is well suited for modern architectures and allows decoupling the business logic from the real-time transport layer.
Several official client SDKs for browser and mobile development wrap the bidirectional protocol. In addition, Centrifugo supports a unidirectional approach for simple use cases with no SDK dependency.
For details, go to the Centrifugo documentation site.
What's changed
Improvements
- Avoid keeping zero offsets in history meta hash keys in Redis – slightly reduces memory consumption of Redis, see centrifugal/centrifuge#332
Fixes
- Centrifugo v5.1.1 fixed
Lua redis lib command arguments must be strings or integers script
error for new Centrifugo setups and new keys in Redis, but have not provided solution to existing keys. In centrifugal/centrifuge/#331 we fixed it. - Updating
github.com/redis/rueidis
to v1.0.22 fixes unaligned atomics to run Centrifugo with Redis engine on 32-bit systems, some details
Misc
- Opentelemetry dependencies updated
- We now have a bash script for quick local setup of Redis cluster - to simplify development
v5.1.1
Centrifugo is an open-source scalable real-time messaging server. Centrifugo can instantly deliver messages to application online users connected over supported transports (WebSocket, HTTP-streaming, SSE/EventSource, GRPC, SockJS, WebTransport). Centrifugo has the concept of a channel – so it's a user-facing PUB/SUB server.
Centrifugo is 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. It is well suited for modern architectures and allows decoupling the business logic from the real-time transport layer.
Several official client SDKs for browser and mobile development wrap the bidirectional protocol. In addition, Centrifugo supports a unidirectional approach for simple use cases with no SDK dependency.
For details, go to the Centrifugo documentation site.
What's changed
Improvements
- Option to extract client connection user ID from HTTP header #730. See documentation for it.
- Speed up channel config operations by using atomic.Value and reduce allocations upon channel namespace extraction by using channel options cache, #727
- New metrics for the size of messages sent and received by Centrifugo real-time transport. Transport messages metrics also include
frame_type
resolution. Finally all the metrics exposed by Centrifugo are described in docs - see Server observability -> Exposed metrics
Fixes
- Fix
Lua redis lib command arguments must be strings or integers script
error when calling Redis reversed history and the stream metadata key does not exist, #732 - Fix Centrifugo logo image link in our Grafana dashboard - new revision uploaded
Misc
- Dependencies updated (rueidis, quic-go, etc)
- Improved logging for bidirectional emulation transports and unidirectional transports - avoid unnecessary error logs
- If you represent a business and using Centrifugo - see also the release of Centrifugo PRO v5.1.1
v5.1.0
Centrifugo is an open-source scalable real-time messaging server. Centrifugo can instantly deliver messages to application online users connected over supported transports (WebSocket, HTTP-streaming, SSE/EventSource, GRPC, SockJS, WebTransport). Centrifugo has the concept of a channel – so it's a user-facing PUB/SUB server.
Centrifugo is 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. It is well suited for modern architectures and allows decoupling the business logic from the real-time transport layer.
Several official client SDKs for browser and mobile development wrap the bidirectional protocol. In addition, Centrifugo supports a unidirectional approach for simple use cases with no SDK dependency.
For details, go to the Centrifugo documentation site.
What's changed
Improvements
- Support for EC keys in JWK sets and EC JWTs when using JWKS #720 by @shaunco, JWKS docs updated
- Experimental GRPC proxy subscription streams #722 - this is like Websocketd but on network steroids 🔥. Streaming request semantics - both unidirectional and bidirectional – is now super-simple to achieve with Centrifugo and GRPC. See additional details about motivation, design, scalability concerns and basic examples in docs, and we provided standalone example for Go backend to experiment with
- Transport error mode for server HTTP and GRPC APIs #690 - read more in docs
- Support GRPC gzip compression #723. GRPC servers Centrifugo has now recognize gzip compression, proxy requests can optionally use compression for calls (see updated proxy docs).
Misc
- Release is built with Go 1.21.3
- Dependencies updated (crypto, otel, msgpack, etc)
New Contributors
Full Changelog: v5.0.4...v5.1.0
v5.0.4
Centrifugo is an open-source scalable real-time messaging server. Centrifugo can instantly deliver messages to application online users connected over supported transports (WebSocket, HTTP-streaming, SSE/EventSource, GRPC, SockJS, WebTransport). Centrifugo has the concept of a channel – so it's a user-facing PUB/SUB server.
Centrifugo is 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. It is well suited for modern architectures and allows decoupling the business logic from the real-time transport layer.
Several official client SDKs for browser and mobile development wrap the bidirectional protocol. In addition, Centrifugo supports a unidirectional approach for simple use cases with no SDK dependency.
For details, go to the Centrifugo documentation site.
What's changed
Improvements
- Support
expire_at
field of SubscribeResult from Subscribe Proxy #707. See description of subscribe result in docs - Option to skip client token signature verification #708, see in docs
Fixes
- Fix connecting to Redis server over unix socket - inherited from centrifugal/centrifuge#318 by @tie
Misc
- Release is built with Go 1.21.1
- Dependencies updated (centrifuge, quic-go, grpc, and others)
v5.0.3
Centrifugo is an open-source scalable real-time messaging server. Centrifugo can instantly deliver messages to application online users connected over supported transports (WebSocket, HTTP-streaming, SSE/EventSource, GRPC, SockJS, WebTransport). Centrifugo has the concept of a channel – so it's a user-facing PUB/SUB server.
Centrifugo is 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. It is well suited for modern architectures and allows decoupling the business logic from the real-time transport layer.
Several official client SDKs for browser and mobile development wrap the bidirectional protocol. In addition, Centrifugo supports a unidirectional approach for simple use cases with no SDK dependency.
For details, go to the Centrifugo documentation site.
What's changed
Improvements
- Add support for GRPC exporter protocol in opentelemetry tracing, by @SinimaWath in #691. Can be enabled by setting
OTEL_EXPORTER_OTLP_PROTOCOL
environment variable, see updated doc
Misc
- Release is built with Go 1.20.7
- Dependencies updated (rueidis, quic-go, opentelemetry, etc)
New Contributors
- @SinimaWath made their first contribution in #691
Full Changelog: v5.0.2...v5.0.3
v5.0.2
Centrifugo is an open-source scalable real-time messaging server. Centrifugo can instantly deliver messages to application online users connected over supported transports (WebSocket, HTTP-streaming, SSE/EventSource, GRPC, SockJS, WebTransport). Centrifugo has the concept of a channel – so it's a user-facing PUB/SUB server.
Centrifugo is 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. It is well suited for modern architectures and allows decoupling the business logic from the real-time transport layer.
Several official client SDKs for browser and mobile development wrap the bidirectional protocol. In addition, Centrifugo supports a unidirectional approach for simple use cases with no SDK dependency.
For details, go to the Centrifugo documentation site.
What's changed
Improvements
- Quiet mode and no expiration for gentoken/gensubtoken cli commands #681 - so token generation using cli helpers is more flexible now
- Add
proxy_static_http_headers
option andstatic_http_headers
key for granular proxy #687 - so it's possible to append custom headers to HTTP proxy requests.
Fixes
- Suppress warnings about k8s env vars, see issue
Misc
- Release is built with Go 1.20.7
- Dependencies updated (rueidis, quic-go, crypto, etc)
- Replace
interface{}
withany
in code base, #682
v5.0.1
Centrifugo is an open-source scalable real-time messaging server. Centrifugo can instantly deliver messages to application online users connected over supported transports (WebSocket, HTTP-streaming, SSE/EventSource, GRPC, SockJS, WebTransport). Centrifugo has the concept of a channel – so it's a user-facing PUB/SUB server.
Centrifugo is 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. It is well suited for modern architectures and allows decoupling the business logic from the real-time transport layer.
Several official client SDKs for browser and mobile development wrap the bidirectional protocol. In addition, Centrifugo supports a unidirectional approach for simple use cases with no SDK dependency.
For details, go to the Centrifugo documentation site.
What's changed
This release contains a fix for Centrifugo v5 released yesterday which prevents server from crashing in case of using subscription tokens.
Fixes
- Fix panic upon subscription token validation caused by nil interface comparison, commit
v5.0.0 💻✨🔮✨💻
Centrifugo is an open-source scalable real-time messaging server. Centrifugo can instantly deliver messages to application online users connected over supported transports (WebSocket, HTTP-streaming, SSE/EventSource, GRPC, SockJS, WebTransport). Centrifugo has the concept of a channel – so it's a user-facing PUB/SUB server.
Centrifugo is 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. It is well suited for modern architectures and allows decoupling the business logic from the real-time transport layer.
Several official client SDKs for browser and mobile development wrap the bidirectional protocol. In addition, Centrifugo supports a unidirectional approach for simple use cases with no SDK dependency.
For details, go to the Centrifugo documentation site.
What's changed in Centrifugo v5 🔥🔥🔥
In Centrifugo v5 we're phasing out old client protocol support, introducing a more intuitive HTTP API, adjusting token management behaviour in SDKs, improving configuration process, and refactoring the history meta ttl option. As the result you get a cleaner, more user-friendly, and optimized Centrifugo experience.
All the major details about the release may be found in Centrifugo v5 release announcement in our blog.
We've also prepared Centrifugo v5 migration guide which has more specific details about changes.
Misc
- This release is built with Go 1.20.5
v4.1.5
Centrifugo is an open-source scalable real-time messaging server. Centrifugo can instantly deliver messages to application online users connected over supported transports (WebSocket, HTTP-streaming, SSE/EventSource, GRPC, SockJS, WebTransport). Centrifugo has the concept of a channel – so it's a user-facing PUB/SUB server.
Centrifugo is 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. It is well suited for modern architectures and allows decoupling the business logic from the real-time transport layer.
Several official client SDKs for browser and mobile development wrap the bidirectional protocol. In addition, Centrifugo supports a unidirectional approach for simple use cases with no SDK dependency.
For details, go to the Centrifugo documentation site.
Release notes
Improvements
- DEB release for Ubuntu Jammy, by @diasjorge
Fixes
- Fix sending usage stats: handle max values reset race, fixes #667