6 ms·
Kafka is very much a boring Java technology, and one that's pretty bad as well.
by mgaunard 3y ago
Kafka is very much a boring Java technology, and one that's pretty bad as well.
- tormeh 3y agoI disagree with all three claims.
- mgaunard 3y agoVoting -1 might have been a better response; alternatively you might have phrased things in a way that requests an answer, or at least articulate your argument. The Kafka being Java one is the most difficult one to refute I'd say.
- woo-loo 3y agoWould you recommend something less boring for scale?
- mgaunard 3y agoAeron maybe, also Java-friendly.
- speed_spread 3y agoAeron is for a pretty different use case. Kafka is optimized for volume batches, Aeron is for very low latency transactional. I wouldn't use one in place of the other. They have very different operational requirements too.
- mgaunard 3y agoBoth are technologies to transport messages over the network in a topic-oriented producer/consumer fashion, and both provide the ability to record and replay from a specific point.
- Tainnor 3y agoI don't think that Kafka is bad per se, it's just that it's often used as a message queue which it doesn't seem optimised for. Half of the stuff you need for a proper MQ (e.g. DLT handling) isn't provided by Kafka proper (although interestingly it is provided by spring-kafka - but that locks you into that tech and just means another abstraction which makes things harder to understand). Also, Kafka doesn't really deal well with long-running consumers, something that might be quite necessary for many async systems.