4 ms·
I wonder... how many issues was Kafka "soaking up" by dealing with concerns that applications and services didn't have to even consider? As in, I wonder how mu
by sigwinch28 4y ago
I wonder... how many issues was Kafka "soaking up" by dealing with concerns that applications and services didn't have to even consider?
As in, I wonder how much application developer burden would be present if using MQTT instead.
- justinclift 4y agoIt's an interesting question. No idea how to go about quantifying it though.
- sigwinch28 4y agoFair.
- JUNGLEISMASSIVE 4y ago[dead]
- tsss 4y agoThe vast majority of "Kafka problems" (or rather "Kafka Streams problems") we have with a managed solution at work are due to not fully understanding how it works and how to set it up. There's so much stuff you can configure and so much potential to misuse it. Typical problems are wrong configuration for acks, not understanding durability guarantees, not understanding exactly-once semantics, not naming hidden topics in Kafka Streams, not using schema registry serializers for hidden topics, choosing the wrong partitioning scheme (and wanting to change it later), using Kafka clients with different hash functions, using wrong schema compatibility mode, etc. etc.