

Apache Kafka and Amazon MSK compete in the real-time data streaming category. Amazon MSK has the upper hand with its managed infrastructure and integration with AWS services, simplifying management tasks for businesses.
Features: Apache Kafka provides high throughput data processing, supports diverse programming languages, and benefits from a strong community. Amazon MSK offers seamless AWS integration, automated management, and comprehensive monitoring capabilities.
Room for Improvement: Apache Kafka could improve by offering more management simplicity and reducing configuration complexity. Enhanced documentation and native managed cloud capabilities could be beneficial. Amazon MSK might improve by expanding its integration capabilities beyond the AWS ecosystem, providing more transparent cost structures, and offering more granular scaling options.
Ease of Deployment and Customer Service: Amazon MSK eases deployment with automation and provides robust AWS customer support. Apache Kafka requires more configuration expertise, leveraging support from third-party vendors or internal teams for deployment, which allows for custom implementations.
Pricing and ROI: Apache Kafka, being open-source, has lower initial costs but can incur higher maintenance expenses, with ROI dependent on available technical resources. Amazon MSK offers usage-based pricing within AWS, potentially enhancing ROI through decreased resource requirements and operational risks.
I can say we have noticed a strong return on investment largely due to improved scalability and reduced operational friction in asynchronous workflows.
They can manage most of our queries, and for what they cannot manage, they guide us through the process of finding out.
Amazon's support is excellent.
Practically, the biggest support channels are its community ecosystem, documentation, GitHub discussions, and engineering forums.
The Apache community provides support for the open-source version.
There is plenty of community support available online.
The functionality for scaling comes out of the box and is very effective.
As a B2B enterprise client, our clientele consists of large ticket clients but low amounts of users.
Customers have not faced issues with user growth or data streaming needs.
For traffic spikes, Apache Kafka naturally helps by buffering events, allowing consumers to catch up instead of immediately overwhelming downstream services.
I need to enable my solution with high availability and scalability.
It doesn't require any maintenance on my end yet, as I haven't had any issues.
Testing changes in lower environments before production rollout and verifying replication health and cluster stability is essential.
Apache Kafka is stable.
This feature of Apache Kafka has helped enhance our system stability when handling high volume data.
The increase in cloud costs by 50% to 60% does not justify the savings.
The only issue with Amazon MSK that we are facing is the configurations.
I had to remove and drop all the clusters and recreate them again, which is complicated in a production environment.
The performance angle is critical, and while it works in milliseconds, the goal is to move towards microseconds.
Running and maintaining an Apache Kafka cluster at scale involves handling partitions, replications, retention policies, rebalancing, and monitoring, which requires strong expertise.
Apache Kafka groups could introduce themes or profiles of configuration to help manage this complexity without needing expertise.
Once we started using Kafka, our cloud costs rose by 50% to 60%.
We use Kafka M5 Large instance, and depending on the instances, that is the cost we have, along with storage cost and data transfer costs.
From a price perspective, if you are asking about Apache Kafka, I would rate it a nine.
The open-source version of Apache Kafka results in minimal costs, mainly linked to accessing documentation and limited support.
Its pricing is reasonable.
The scalability and usability are quite remarkable.
The best features of Amazon MSK are the real-time analytics that are excellent.
Amazon MSK is basically Kafka in the cloud, and when you need to create a cluster of Kafka brokers, Amazon MSK helps with that by automatically creating all the brokers according to the configuration you provide.
Apache Kafka is effective when dealing with large volumes of data flowing at high speeds, requiring real-time processing.
Apache Kafka is particularly valuable for managing high levels of transactions.
Regarding durability and reliability, messages are persisted, so temporary consumer failures do not automatically lead to data loss, which is valuable in financial workflows where losing events is unacceptable.
| Product | Mindshare (%) |
|---|---|
| Apache Kafka | 3.8% |
| Amazon MSK | 4.0% |
| Other | 92.2% |


| Company Size | Count |
|---|---|
| Small Business | 4 |
| Midsize Enterprise | 7 |
| Large Enterprise | 5 |
| Company Size | Count |
|---|---|
| Small Business | 32 |
| Midsize Enterprise | 20 |
| Large Enterprise | 51 |
Amazon MSK offers seamless AWS integration, simplifying development and operation. It supports efficient data streaming and ensures cost-effective scalability without additional setup needs.
Amazon MSK stands out for its effortless creation, deployment, and access to new features without complex VPC configurations. Automating scalability, it demands minimal intervention, making it ideal for high-volume workflows. Developers benefit from real-time analytics, event sourcing, and log ingestion, aiding in dashboard maintenance and user log tracking. However, integration challenges exist as some face inflexibility, intricate configurations, and plugin development difficulties. Schema validation, connector variety, and complex update processes lead some to seek alternatives. Noteworthy for order data streaming, transaction tracking in retail and banking, and other real-time data applications, Amazon MSK remains attractive despite high cost concerns.
What are Amazon MSK's key features?In retail and banking, Amazon MSK facilitates order data streaming and transaction tracking. Its capabilities in supporting CDC pipelines, high-volume data management, and asynchronous processes make it favorable for integrating systems, streaming IoT data, and managing dashboard flows. Challenges in integration and configuration persist, nudging users to explore different options in certain contexts.
Apache Kafka provides scalable, high-throughput, real-time data processing. Appreciated for its open-source nature and integration capabilities, Kafka supports distributed messaging and high-volume handling with essential features like message retention, replication, and partitioning.
Apache Kafka is a powerful tool for managing efficient data streams and high volumes of asynchronous messages. Its ease of setup and robust integration options make it popular among industries requiring real-time data streaming and processing. Key features such as message retention and consumer groups cater to demanding applications, while fault-tolerant design ensures reliability. Despite its advantages, Kafka can improve in areas like duplicate management, documentation, and intuitive interfaces. Challenges in configuration and monitoring tools suggest areas for enhancement, alongside reducing complexity and resource dependency.
What are the key features of Apache Kafka?Industry applications for Apache Kafka include real-time data streaming for IoT, big data management, and analytics. In finance, it supports fraud detection and transaction monitoring. Healthcare uses Kafka for patient data handling and logistics leverage its data distribution capabilities to optimize operations. Its ability to manage large-scale asynchronous communication makes it vital across sectors demanding high data throughput and reliability.
We monitor all Streaming Analytics reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.