🚨 Big shake-up for MSK users → AWS is requiring ZooKeeper-based clusters to migrate to KRaft. No in-place upgrade option, meaning a full migration is mandatory: If you’re going to be forced into a migration anyway, it’s a good time to pause and ask: 👉 Do you really want to double down on Kafka’s operational overhead? 👉 Or is this the moment to look at alternatives built for simpler scaling and lower cost? That’s exactly why a lot of teams have shifted to Pulsar with StreamNative, separating compute and storage, built-in multi-tenancy, geo-replication, and zero-downtime scaling without leader elections. Sometimes a vendor’s “end of life” push is the perfect chance to rethink whether the old architecture is worth the pain. If you’re running Kafka/MSK today, how are you thinking about this forced migration? #Kafka #Pulsar #Streaming #AWS #DataEngineering
Doomsday is coming for MSK users. you must migrate or face end of life... MSK is forcing users to migrate to a KRaft cluster rather than doing an in place upgrade from their existing ZooKeeper clusters. If you're going to migrate.. you might as well come on over to WarpStream which is easier to scale, supported by folks who actually know Kafka, and costs less to boot. We have tools to make the migration easier as well :) https://lnkd.in/gp5bqM7G
