3 ms·

Correct; but I've seen many uses of Kafka that NATS could totally be used for. For example, load balancing across subscribers (use a NATS queue instead of a Kaf

by cmckn 6y ago

Correct; but I've seen many uses of Kafka that NATS could totally be used for. For example, load balancing across subscribers (use a NATS queue instead of a Kafka consumer group). NATS doesn't ever store messages persistently; but this might be fine for your application, and then you don't have to worry about setting 5 different config options to make sure Kafka actually frees up disk space like you expect it to ;) NATS also enables some unique patterns like request/reply via a "reply to" message header. Anyway, it's been a joy to use!

KptMarchewa 6y ago
Sounds more like rabbitmq replacement than kafka
tamale 6y ago
you also don't have to worry about those kinds of configuration gotchas if you use confluent cloud!
- jimmyed 6y ago
  Only you have to be a billionaire to use the confluent cloud.
  - incognito_limey 6y ago
    So I guess pay as you go is too expensive for your org? Be curious to understand why you feel it's too expensive when it completely extrapolates any kafka management.
    - stalller 6y ago
      relative to more mature Kafka cloud services, it's crazy expensive.
shaklee3 6y ago
> NATS doesn't ever store messages persistently Not true. Both Nats streaming and the upcoming jetstream (core nats) do.
- tsimionescu 6y ago
  It depends what you mean by 'persistently'. Normally NATS streaming will delete the messages after they have been delivered to all subscribers successsfully and some expiration time has passed.
  - shaklee3 6y ago
    The expiration time can be unlimited, just like kafka
- cmckn 6y ago
  I'm aware, I was referring to the core binary, `nats-server`. NATS streaming server seems to be still receiving attention, but the client library (for Java) hasn't been committed to since 2019, so I'm not sure I'd build a new project with it. JetStream is out (as of this week, I believe) and is an optional module to `nats-server`, as you said. To the folks at Synadia -- I love NATS, but the naming and organization of these projects could use some work. What's with the `stan.*` repository names? Where did "jetstream" come from? Why is it baked into `nats-server` but `nats-streaming-server` isn't? Is `nats-streaming-server` on the back burner?
  - shaklee3 6y ago
    Stan is nats streaming. The clients don't have to be updated since they're forward compatible since jetstream. NATS streaming will be deprecated after jetstream is GA is my understanding. Is there a bug in the library you found?

by cmckn 6y ago

KptMarchewa 6y ago

Sounds more like rabbitmq replacement than kafka

tamale 6y ago

you also don't have to worry about those kinds of configuration gotchas if you use confluent cloud!

jimmyed 6y ago
Only you have to be a billionaire to use the confluent cloud.
- incognito_limey 6y ago
  So I guess pay as you go is too expensive for your org? Be curious to understand why you feel it's too expensive when it completely extrapolates any kafka management.
  - stalller 6y ago
    relative to more mature Kafka cloud services, it's crazy expensive.

shaklee3 6y ago

> NATS doesn't ever store messages persistently Not true. Both Nats streaming and the upcoming jetstream (core nats) do.

tsimionescu 6y ago
It depends what you mean by 'persistently'. Normally NATS streaming will delete the messages after they have been delivered to all subscribers successsfully and some expiration time has passed.
- shaklee3 6y ago
  The expiration time can be unlimited, just like kafka
cmckn 6y ago
I'm aware, I was referring to the core binary, `nats-server`. NATS streaming server seems to be still receiving attention, but the client library (for Java) hasn't been committed to since 2019, so I'm not sure I'd build a new project with it. JetStream is out (as of this week, I believe) and is an optional module to `nats-server`, as you said. To the folks at Synadia -- I love NATS, but the naming and organization of these projects could use some work. What's with the `stan.*` repository names? Where did "jetstream" come from? Why is it baked into `nats-server` but `nats-streaming-server` isn't? Is `nats-streaming-server` on the back burner?
- shaklee3 6y ago
  Stan is nats streaming. The clients don't have to be updated since they're forward compatible since jetstream. NATS streaming will be deprecated after jetstream is GA is my understanding. Is there a bug in the library you found?