rcombatwombat

5 ms·

1.
by rcombatwombat 11mo ago
So that makes their contribution to Zig a bad thing?
2.
by rcombatwombat 1y ago
Still not what I would call 'proper' queuing (IMHO!) because ultimately it's still just Kafka and just append only: you can't 'atomically acknowledge+delete' individual messages anywhere in the stream, you only
3.
by rcombatwombat 1y ago
Let's not forget NATS.io which does queuing (and a whole lot of other things from at least once low latency pub/sub to request/reply, streaming and all the way to KV and Object store) very well and is very light weight to run
4.
by rcombatwombat 1y ago
No rug pull: https://www.cncf.io/announcements/2025/05/01/cncf-and-synadi...
5.
by rcombatwombat 1y ago
Two points: From the exit proposal: "Over 97% of contributions to the NATS.io server were made by employees of Synadia and its predecessor company". Also, when they applied for graduation in 2018, they were told no because most o
6.
by rcombatwombat 2y ago
IMHO NATS is an even better Swiss army knife than Rabbit
7.
by rcombatwombat 2y ago
NATS does much more than pub/sub (with any fan out), it also does queueing in Core NATS (no persistence) and streaming including queuing over streams (with ack/nack/term). Don't be fooled into thinking NATS doesn't
8.
by rcombatwombat 2y ago
Yes, one of the many differences (advantages) of NATS JetStream over Kafka: with NATS you can ack explicitly each message individually, and even better if you set your stream to be in 'work-queue' mode it will also automatically (
9.
by rcombatwombat 3y ago
NATS with JetStream provides _both_ queuing like a traditional message broker and multiple data replay from offset (plus KV, and request/reply)
10.
by rcombatwombat 3y ago
Also see https://www.youtube.com/watch?v=C4BnJ5QLeTY
11.
by rcombatwombat 3y ago
NATS JetStream also implements subject-based addressing at the stream level (unlike Kafka where 1 stream = 1 topic, and you can only use the message's key for distribution, not for addressing). So you can for example ask for [the first
12.
by rcombatwombat 3y ago
The 'auth callout' feature introduced in NATS 2.10 is there exactly for that (integrating NATS auth with whatever existing IdP system you already have): the client app passes whatever you use as it's credentials at connection
13.
by rcombatwombat 3y ago
It supports clients connecting over TCP (which can be encrypted) and Websockets (can also be encrypted), you can configure it to pick on any port you want and it works through Network Address Translation (see https://docs.nats.io
14.
by rcombatwombat 3y ago
IMHO and I would argue that JetStream functionally does much more than Apache Kafka (e.g. stream filtering using subject based addressing, stream with working queue semantics, constraints on streams, compare and set (so you can do CRUD oper
15.
by rcombatwombat 3y ago
See https://github.com/nats-io/nats.go/tree/main/jetstream#readm...
16.
by rcombatwombat 3y ago
(note that NATS Streaming is a now deprecated predecessor to NATS JetStream) Pull does have advantages over push (e.g. one-to-one flow control since the transfer of the messages is initiated by the client (pull requests)), and they are basi