> Maybe in hyper-scaled applications that need to be ultraperformant (e.g., realtime trading, massive streaming platforms) is where Kafka comes into play.

Kafka is used because the Java folks don't want to learn something new due to job security, even though there are faster and compatible alternatives that exist today.

Rather use Redpanda, than continue to use Kafka and then complain about how resource intensive it is alongside zookeeper and all the circus the comes with it and make AWS smile as you're losing hundreds of thousands a month.

▲

AtlasBarfed 4 days ago | parent [-]

I thought Kafka ditched the zookeeper

▲

mdaniel 3 days ago | parent [-]

I wish; KIP-500[1] was the "let's use native Raft" implementation but I have never once in my life seen anyone using Kafka in KIP-500 mode

1: https://cwiki.apache.org/confluence/display/kafka/kip-500:+r...

	▲	enether 3 days ago \| parent \| next [-]
		Confluent has shared they've migrated thousands of Kafka clusters (their whole cloud fleet) to KIP-500 https://www.confluent.io/blog/zookeeper-to-kraft-with-conflu...
	▲	62951413 2 days ago \| parent \| prev [-]
		Very few people want to re-create their production AWS MSK cluster from scratch. And that's the only way currently. MSK can usually upgrade Kafka brokers with minor performance degradation but not for this particular change.