Source ref:https://www.reddit.com/r/apachekafka/comments/198sftu/kafka_vs_nats_jetstream/

[kharabela]

One user posted this in forum.
I am curious to know the workarounds for these issues.Just FYI, I am liking NATS so far and have reads people using it in Production.
Apart from wide community as compared to Kafka.Can you provide inputs in the below issues posted by the user.

We have a project using Kafka and one using NATS Jetstream. (No NATS core usage)
For us there was not much difference in the effort for hosting the two.
Main difference is for us the stability, especially about the client libraries:
Kafka and the client libraries seems to be much more stable

We had and still have issues on NATS Jetstream with Consumers
Eg.: Consumer is connected but at a certain time does not receive any messages -> library reports connected, no error / warning logs -> only restart helps
Never had such issues with Kafka
Message de-duplication for failed acknowledgements need to be handled manually
Kafka seems to better fit our use cases
NATS Jetstream does not allow ordering within a subject across multiple consumers
Kafka supports this with partition ids which guarantees execution in order on one consumer for a specific partition id
This is a major downside of NATS Jetstream and leads to complicated designs / workarounds
Kafka has better integrations and bigger community
Kafka documentation is much more detailed and precise
NATS allows more flexibility with Consumers and subjects
Eg.: Easier wildcard subscriptions, Ephemeral consumers, ...
As mentioned this is only a comparison for KAFKA and NATS Jetstream.
NATS core is a different concept for different use cases.