Viewing profile — rcombatwombat
rcombatwombat
HN member- Joined
- Mon, Jul 24, 2023, 10:36 PM UTC
- HN karma
- 10
- Public activity
- 16 items
- HN profile
- View on Hacker News ↗
About rcombatwombat
No profile information was provided.
Recent public activity
-
comment
Comment #45713665
So that makes their contribution to Zig a bad thing?
-
comment
Comment #45074050
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 an…
-
comment
Comment #45073943
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 sto…
-
comment
Comment #43917002
No rug pull: https://www.cncf.io/announcements/2025/05/01/cncf-and-synadi...
-
comment
Comment #43788997
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 gra…
-
comment
Comment #43163783
IMHO NATS is an even better Swiss army knife than Rabbit
-
comment
Comment #43163759
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…
-
comment
Comment #42404208
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…
-
comment
Comment #37617832
NATS with JetStream provides _both_ queuing like a traditional message broker and multiple data replay from offset (plus KV, and request/reply)
-
comment
Comment #37606163
Also see https://www.youtube.com/watch?v=C4BnJ5QLeTY
-
comment
Comment #37605961
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…
-
comment
Comment #36855532
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 whate…
-
comment
Comment #36855473
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 Netw…
-
comment
Comment #36855418
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, cons…
-
comment
Comment #36855345
See https://github.com/nats-io/nats.go/tree/main/jetstream#readm...
-
comment
Comment #36855329
(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…