FZambia

6 ms·

1.
by FZambia 3mo ago
Thanks! Our users mostly run Redis or Valkey, so we optimize for them. We also have Dragonflydb in our test suite. But good to know there is one more option which may be used as a drop in replacement for Redis and provide extra properties,
2.
Scaling Redis Pub/Sub across many active channels and nodes(centrifugal.dev)
2 points by FZambia 3mo ago|2 comments
3.
Recreating a Two Million Particle World at 30 Hz over WebSocket with Centrifugo(centrifugal.dev)
2 points by FZambia 4mo ago|0 comments
4.
by FZambia 1y ago
Many here recommend using Kafka or RabbitMQ for real-time notifications. While these tools work well with a relatively stable, limited set of topics, they become costly and inefficient when dealing with a large number of dynamic subscribers
5.
by FZambia 1y ago
Client SDKs are often a major challenge in systems like these. In my experience, building SDKs on top of asynchronous protocols is particularly tricky. It's generally much easier to make the server-side part reliable. The complexity ar
6.
by FZambia 1y ago
For real-time notifications, I believe Nats ( https://nats.io ) or Centrifugo ( https://centrifugal.dev ) are worth checking out these days. Messages may be delivered to those systems from PostgreSQL over replication pro
7.
by FZambia 2y ago
Hi everyone! I'd like to share that we've just released Centrifugo v6 - a major update of scalable WebSocket server. The release addresses some usability pain points and adds nice features and more observability. Centrifugo is an
8.
Centrifugo v6 released – major update of scalable WebSocket server written in Go(centrifugal.dev)
2 points by FZambia 2y ago|1 comments
9.
by FZambia 2y ago
Yep, and in addition to that the ephemeral ports problem will araise at some scale with long-lived connections and infrastructure balancer/reverse proxy chain. So it's still required to tune.
10.
by FZambia 2y ago
Wow, it's fascinating how a single HN comment can drive meaningful traffic to a project! I'm the author of Centrifugo, and I appreciate you mentioning it here. Let me share a bit more about Centrifugo transport choices. It’s not j
11.
Early draft discussion of memory regions for Go language to reduce GC overhead(github.com)
4 points by FZambia 2y ago|0 comments
12.
Performance optimizations of WebSocket compression in Go application(centrifugal.dev)
1 points by FZambia 2y ago|0 comments
13.
Resolving 6 key Jetpack Compose UI testing problems(medium.com)
1 points by FZambia 2y ago|0 comments
14.
by FZambia 2y ago
Hello, I am author of https://github.com/centrifugal/centrifugo . Our users can choose from WebSocket, EventSource, WebTransport (experimental for now, but will definitely stabilize in the future). WebRTC is out of scop
15.
Show HN: Scalable instant messaging app with Django (source code and tutorial)(github.com)
3 points by FZambia 3y ago|0 comments
16.
Ask HN: WebSocket server transforming channel subscriptions to gRPC streams
1 points by FZambia 3y ago|0 comments
17.
by FZambia 3y ago
Wondering whether coroutines may be a step towards async event-based style APIs without allocating read buffers for the entire connection. I.e. a solution to problems discussed in https://github.com/golang/go/issue
18.
Deleted
1 points by FZambia 4y ago|0 comments
19.
by FZambia 5y ago
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
20.
Centrifugo v3 released – new skills of the real-time messaging server(centrifugal.dev)
2 points by FZambia 5y ago|0 comments
21.
by FZambia 6y ago
Hi! Could you please extend the meaning of word "global-scale" a bit? Does this only mean that users will connect to the nearest server or there are more tricks on backend to scale PUB/SUB? You are writing that "messages
22.
An introduction to Centrifuge – real-time messaging with Go(centrifugal.github.io)
2 points by FZambia 6y ago|0 comments
23.
Show HN: Centrifuge – real-time messaging library for Go language(github.com)
2 points by FZambia 6y ago|0 comments
24.
Experimenting with QUIC and WebTransport in Go(centrifugal.github.io)
5 points by FZambia 6y ago|0 comments
25.
Centrifugo – scalable real-time messaging server in language-agnostic way(centrifugal.github.io)
2 points by FZambia 6y ago|0 comments
26.
by FZambia 6y ago
Thanks for feedback, I thought the article left fully unnoticed here:) Go also has a small disadvantage for writing WebSocket apps – you don't have full control on read buffer reuse (since its got allocated for entire lifetime of conne
27.
Scaling WebSocket in Go and Beyond(centrifugal.github.io)
5 points by FZambia 6y ago|2 comments
28.
by FZambia 6y ago
I also don't really like new design of main repo page. Repo short description on the right – so inconvenient. BTW this is how it looks on mobile: https://i.imgur.com/SqV23WN.jpg - the most interesting things about repo
29.
Show HN: Centrifugo v2.4.0 released, server-side subscriptions introduced(github.com)
4 points by FZambia 7y ago|0 comments
30.
Centrifugo – scalable real-time messaging in language-agnostic way(github.com)
2 points by FZambia 7y ago|0 comments

More ›