4 ms·

Have you tried nats.io and it’s new streaming tech, Jetstream? Night and day difference in terms of management and ease of use. In my last org I was fighting so

Have you tried nats.io and it’s new streaming tech, Jetstream? Night and day difference in terms of management and ease of use. In my last org I was fighting so hard against folks wanting to adopt Kafka, and then I found out about nats, total game changer

igetspam 4y ago
Or Redpanda. We like to think it's Kafka but better. Obvious bias: I work for Redpanda
- SushiMon 4y ago
  NATS is open source and CNCF. Redpanda is more a SaaS -- if it goes away, so does your app.
  - FridgeSeal 4y ago
    I don’t think that holds here, Redpanda has a Kafka compatible API layer and you can 100% self-host it. Being CNCF or not doesn’t seem like a meaningful or useful distinction here.
    - EdwardDiego 4y ago
      The compatibility isn't 100% there yet.
  - igetspam 4y ago
    https://github.com/redpanda-data/redpanda https://github.com/redpanda-data/redpanda You're welcome to use it yourself and not pay us a dime. We're a business so we need to monetize but our core is to build a better Kafka. The nice thing is that if you've already invested in building against Kafka but you're exhausted by running Kafka, ours works better and faster. (Again, I'm biased so don't trust me, verify.)
FridgeSeal 4y ago
NATS and Kafka offer different semantics. By default, NATS offers non durable messages and different delivery options. I believe you could get durable messages, but last time I read up on this, it required running extra features or infrastructure to support this.
- codegangsta 4y ago
  You now get durability on whatever subjects you want via NATS Jetstream: https://docs.nats.io/nats-concepts/jetstream https://docs.nats.io/nats-concepts/jetstream No additional infrastructure, just enable it on the nodes you want persistence on and create a stream. Publishers don't even have to change, consumers have a great api with lots of options
  - FridgeSeal 4y ago
    Oh that’s pretty cool, I wasn’t aware of that! Nice to that functionality added!

igetspam 4y ago

Or Redpanda. We like to think it's Kafka but better. Obvious bias: I work for Redpanda

SushiMon 4y ago
NATS is open source and CNCF. Redpanda is more a SaaS -- if it goes away, so does your app.
- FridgeSeal 4y ago
  I don’t think that holds here, Redpanda has a Kafka compatible API layer and you can 100% self-host it. Being CNCF or not doesn’t seem like a meaningful or useful distinction here.
  - EdwardDiego 4y ago
    The compatibility isn't 100% there yet.
- igetspam 4y ago
  https://github.com/redpanda-data/redpanda https://github.com/redpanda-data/redpanda You're welcome to use it yourself and not pay us a dime. We're a business so we need to monetize but our core is to build a better Kafka. The nice thing is that if you've already invested in building against Kafka but you're exhausted by running Kafka, ours works better and faster. (Again, I'm biased so don't trust me, verify.)

FridgeSeal 4y ago

NATS and Kafka offer different semantics. By default, NATS offers non durable messages and different delivery options. I believe you could get durable messages, but last time I read up on this, it required running extra features or infrastructure to support this.

codegangsta 4y ago
You now get durability on whatever subjects you want via NATS Jetstream: https://docs.nats.io/nats-concepts/jetstream https://docs.nats.io/nats-concepts/jetstream No additional infrastructure, just enable it on the nodes you want persistence on and create a stream. Publishers don't even have to change, consumers have a great api with lots of options
- FridgeSeal 4y ago
  Oh that’s pretty cool, I wasn’t aware of that! Nice to that functionality added!