Aiven Platform vs Amazon MSK comparison

"What I like best about the tool is that the process for the services is faster compared to other methods. It's easier to use because Aiven for Apache Kafka handles the maintenance, so we have less to manage. We only use Kafka to manage its connectivity."

"It is a stable product."

"The solution's technical support was helpful."

"It offers good stability."

"Overall, it is very cost-effective based on the workflow."

"MSK has a private network that's an out-of-box feature."

"Amazon MSK's scalability is very good."

"Amazon MSK's separation of concerns and ease of creating and deploying new features are highly valuable. It just requires to assign them to the topic, and then anyone who needs to consume these messages can do so directly from Amazon MSK. This separation of concerns makes it very convenient, especially for new feature development, as developers can easily access the messages they need without having to deal with complex server communications or protocol setups."

"Amazon MSK has significantly improved our organization by building seamless integration between systems."

"One challenge we face is when we want to update the version, for example, from 3.6 to 3.7. It will spawn new nodes, and then there's rebalancing and syncing from other brokers. There's high CPU usage during this process, so the solution can't be used for a while, causing some downtime in our services. To tackle this challenge, we schedule maintenance updates during low-traffic periods when there's less risk and fewer users use the services."

"It does not autoscale. Because if you do keep it manually when you add a note to the cluster and then you register it, then it is scalable, but the fact that you have to go and do it, I think, makes it, again, a bit of some operational overhead when managing the cluster."

"Horizontal scale-out is actually not easy, making it an area where improvements are required."

"It would be really helpful if Amazon MSK could provide a single installation that covers all the servers."

"The product's schema support needs enhancement. It will help enhance integration with many kinds of languages of programming languages, especially for environments using languages like .NET."

"It should be more flexible, integration-wise."

"In my opinion, there are areas in Amazon MSK that could be improved, particularly in terms of configuration. Initially setting it up and getting it connected was quite challenging. The naming conventions for policies were updated by AWS, and some were undocumented, leading to confusion with outdated materials. It took us weeks of trial and error before discovering new methods through hidden tutorials and official documentation."

"Amazon MSK could improve on the features they offer. They are still lagging behind Confluence."

"One of the reasons why we prefer Kafka is because the support is a little bit difficult to manage with Amazon MSK."

"The platform has better pricing than one of its competitors."

"When you create a complete enterprise-driven architecture that is deployable on an enterprise scale, I would say that the prices of Amazon MSK and Confluent Platform become comparable."

"The price of Amazon MSK is less than some competitor solutions, such as Confluence."