or kafka, or any other publish/subscribe system
Kafka doesn't guarantee exactly once delivery at all, unless you're using Kafka Streams and even then your final output topic still won't get exactly once, the consumer group protocol doesn't allow for it.
It's cheaper until you get to a sizeable workload, and the P90+ latency is ridiculous.. the kafka api is weak and when you're not using kafka api you're limited on integration tools unless you want to be super locked in…
There is Redis Streams, but certainly not without it's problems. Super obscure, not a lot of client support.
Massive and complex platform.. at a certain point why not just run 2 different platforms that are best of breed for each.
>> Rabbit can do everything Kafka does - and much more - in a more configurable manner. Sure, if you're doing like 10's of MB/s. RMQ is fast compared to AK if you're not adding durability, persistence, etc. Try to run…
They always have.. you get it but you don't know it.
Maybe "it's enterprise" means that's what the enterprise standardized on. There are a couple of practical reasons that come to mind on why that's the case - a) it's more resilient and durable than messaging platforms,…
Also https://jepsen.io/analyses/redpanda-21.10.1
Are you sure performance would be acceptable if you just turned on fsync on every message?
or kafka, or any other publish/subscribe system
Kafka doesn't guarantee exactly once delivery at all, unless you're using Kafka Streams and even then your final output topic still won't get exactly once, the consumer group protocol doesn't allow for it.
It's cheaper until you get to a sizeable workload, and the P90+ latency is ridiculous.. the kafka api is weak and when you're not using kafka api you're limited on integration tools unless you want to be super locked in…
There is Redis Streams, but certainly not without it's problems. Super obscure, not a lot of client support.
Massive and complex platform.. at a certain point why not just run 2 different platforms that are best of breed for each.
>> Rabbit can do everything Kafka does - and much more - in a more configurable manner. Sure, if you're doing like 10's of MB/s. RMQ is fast compared to AK if you're not adding durability, persistence, etc. Try to run…
They always have.. you get it but you don't know it.
Maybe "it's enterprise" means that's what the enterprise standardized on. There are a couple of practical reasons that come to mind on why that's the case - a) it's more resilient and durable than messaging platforms,…
Also https://jepsen.io/analyses/redpanda-21.10.1
Are you sure performance would be acceptable if you just turned on fsync on every message?