Amazon MSK vs Apache Spark Streaming comparison

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

"The solution's technical support was helpful."

"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."

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

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

"Amazon MSK's scalability is very good."

"It is a stable product."

"It offers good stability."

"Apache Spark Streaming's most valuable feature is near real-time analytics. The developers can build APIs easily for a code-steaming pipeline. The solutions have an ecosystem of integration with other stock services."

"Apache Spark Streaming has features like checkpointing and Streaming API that are useful."

"The solution is better than average and some of the valuable features include efficiency and stability."

"Apache Spark Streaming was straightforward in terms of maintenance. It was actively developed, and migrating from an older to a newer version was quite simple."

"It's the fastest solution on the market with low latency data on data transformations."

"As an open-source solution, using it is basically free."

"The platform’s most valuable feature for processing real-time data is its ability to handle continuous data streams."

"The solution is very stable and reliable."

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

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

"The configuration seems a little complex and the documentation on the product is not available."

"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."

"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."

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

"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."

"The initial setup is quite complex."

"It was resource-intensive, even for small-scale applications."

"The cost and load-related optimizations are areas where the tool lacks and needs improvement."

"The solution itself could be easier to use."

"The debugging aspect could use some improvement."

"There could be an improvement in the area of the user configuration section, it should be less developer-focused and more business user-focused."

"In terms of improvement, the UI could be better."

"The service structure of Apache Spark Streaming can improve. There are a lot of issues with memory management and latency. There is no real-time analytics. We recommend it for the use cases where there is a five-second latency, but not for a millisecond, an IOT-based, or the detection anomaly-based. Flink as a service is much better."

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

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

"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."

"On a scale from one to ten, where one is expensive, or not cost-effective, and ten is cheap, I rate the price a seven."

"I was using the open-source community version, which was self-hosted."

"Spark is an affordable solution, especially considering its open-source nature."

"People pay for Apache Spark Streaming as a service."