relay23

13 ms·

1.
by relay23 3y ago
or kafka, or any other publish/subscribe system
2.
by relay23 3y ago
Sounds about right.
3.
by relay23 3y ago
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.
4.
by relay23 3y ago
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 to GC
5.
by relay23 3y ago
There is Redis Streams, but certainly not without it's problems. Super obscure, not a lot of client support.
6.
by relay23 3y ago
Massive and complex platform.. at a certain point why not just run 2 different platforms that are best of breed for each.
7.
by relay23 3y ago
>> 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
8.
by relay23 3y ago
They always have.. you get it but you don't know it.
9.
by relay23 3y ago
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 pla
10.
by relay23 3y ago
Also https://jepsen.io/analyses/redpanda-21.10.1
11.
by relay23 3y ago
Are you sure performance would be acceptable if you just turned on fsync on every message?
12.
by relay23 4y ago
Almost nobody auto commits offsets in real applications though. If you do then you should really stop :)