No more typing reviews! Try our Samantha, our new voice AI agent.

Apache Kafka on Confluent Cloud vs Kubernetes Everywhere comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Apache Kafka on Confluent C...
Average Rating
8.6
Reviews Sentiment
5.6
Number of Reviews
15
Ranking in other categories
Streaming Analytics (13th)
Kubernetes Everywhere
Average Rating
9.0
Number of Reviews
12
Ranking in other categories
Managed Cloud Services (2nd)
 

Mindshare comparison

Apache Kafka on Confluent Cloud and Kubernetes Everywhere aren’t in the same category and serve different purposes. Apache Kafka on Confluent Cloud is designed for Streaming Analytics and holds a mindshare of 0.7%, up 0.0% compared to last year.
Kubernetes Everywhere, on the other hand, focuses on Managed Cloud Services, holds 6.6% mindshare, up 2.5% since last year.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Apache Kafka on Confluent Cloud0.7%
Apache Flink8.2%
Databricks7.9%
Other83.2%
Streaming Analytics
Managed Cloud Services Mindshare Distribution
ProductMindshare (%)
Kubernetes Everywhere6.6%
HPE GreenLake19.7%
Everpure Evergreen One18.5%
Other55.2%
Managed Cloud Services
 

Featured Reviews

AF
Lead Software Engineer at a tech vendor with 10,001+ employees
Has unified log streams from multiple systems and accelerated issue tracking through streamlined setup
I think Apache Kafka on Confluent Cloud can be improved by probably working more around Confluent or the tool. In my opinion, it should utilize the response structures in a better way or be able to detect if there is any variable or if there is any data structure that is mismatched, as it would be easier than us manually having to put in the exact name in order for it to match the response. Regarding additional improvements, I would say probably around error handling, where when we encounter errors specific to our response structures and everything, or the tables or anything of that nature, it would be better if we were prompted with better error handling mechanisms. I do not think there are any other improvements Apache Kafka on Confluent Cloud needs, aside from error handling and response structures.
Manoday Ahire - PeerSpot reviewer
AWS Cloud Infrastructure Engineer at Reg-X Innovations
Modern deployment practices have reduced downtime and support efficient multi-app management
Kubernetes Everywhere offers features including auto-scaling, which is the best feature, as well as load balancing, ingress controllers, and the ability to host multiple applications on a single Kubernetes Everywhere cluster through segregation using namespaces. The commands are straightforward to execute, and it allows the integration and management of Docker containers efficiently. Auto-scaling is one of the features I use in Kubernetes Everywhere that made a significant impact, helping us with user distribution as the pods scale automatically without disruption as users increase, contributing to high availability and low downtime. I am using Kubernetes Everywhere with the GitOps approach, using Git as a source of truth, which provides excellent security and has made a significant change in our current infrastructure. Kubernetes Everywhere has positively impacted my organization by significantly reducing downtime. We have achieved almost zero minutes of downtime since implementing Kubernetes Everywhere in our organization after transitioning from manual deployments. Regarding cost savings, we were using multiple EC2 instances for different projects, but now everything is under one cluster, running as a pod and segregated by namespaces, leading to cost savings. For team collaboration, we are using different tools with Git as a source of truth, making it easy for developers to manage instances and gain insights efficiently.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The return on investment has been significant, especially in terms of stability, scalability, and the fact that we almost never had any issues in production."
"Confluent helped me to streamline all those logs into one place, and then I was consuming those logs that were produced, which made it very much easier because I know Kafka and using Confluent made it much simpler."
"Overall, I think it's a good experience. Apache Kafka can be quite complex and difficult to maintain on your own, so using Apache Kafka on Confluent Cloud makes it much easier to use it without worrying about setup and maintenance."
"The benefits that I have seen from having a real-time architecture include better velocity for developers; instead of developing many of those capabilities in each team, we can rely on Apache Kafka on Confluent Cloud to provide those functionalities we want, and the teams can focus on their own business instead of providing all sorts of APIs and dependencies to other domains, allowing everyone to run faster."
"Confluent Cloud handles data volume pretty well."
"In case of huge transactions on the web or mobile apps, it helps you capture real-time data and analyze it."
"Kafka and Confluent Cloud have proven to be cost-effective, especially when compared to other tools. In a recent BI integration program over the past year, we assessed multiple use cases spanning ship-to-shore and various Azure integrations. Our findings revealed that Confluent Kafka performed exceptionally well, standing out alongside Genesys and Azure Event Hubs. While these three are top contenders, the choice among other tools depends on the specific use case and project requirements. The customer initially used tools like SMQs, FITRA, and Stream for real-time data processing. However, after our recommendation, Confluent Cloud proved to be a superior choice, capable of replacing these three tools and simplifying their data infrastructure. This shift to a single tool, Confluent Cloud, streamlined their operations, making maintenance and management more efficient for their internal projects."
"Apache Kafka on Confluent Cloud is critical infrastructure for us; without it, our infrastructure costs would increase significantly, potentially amounting to hundreds of thousands of dollars each year, and its real-time capabilities accelerate speed to value and enable new use cases, providing significant business value."
"Kubernetes Everywhere has positively impacted my organization because we do not require any tech background to make our web app work."
"Kubernetes Everywhere is easy to operate when you have a settled environment and easy to manage, offering high availability and fault tolerance with all high availability features, rich support of the latest technologies, vulnerability management, and easy management."
"Kubernetes Everywhere is a premier operational asset for modern multi-cloud architecture, delivering standard, predictable workload orchestration across any underlying hardware engine with minimal setup complexity."
"Kubernetes Everywhere has positively impacted my organization by significantly reducing the time needed to manage clusters and workloads, as we previously required several team members for cluster management, but now it provides a central console to manage everything."
"Kubernetes Everywhere is a very good tool with most of the features taken from Kubernetes open-source, and it works really well, is highly scalable with very low latency."
"Kubernetes Everywhere has impacted my organization positively because performance-wise, we don't have any downtimes, whereas earlier we used to have downtime."
"Kubernetes Everywhere has positively impacted my organization by significantly reducing downtime; we have achieved almost zero minutes of downtime since implementing Kubernetes Everywhere in our organization after transitioning from manual deployments."
"Kubernetes Everywhere positively impacts our organization by making it quite easy to deploy different microservices for different languages; we simply build the Docker container and pass it to the YAML, and if anything breaks, debugging is straightforward because we know exactly where the issue is coming from."
 

Cons

"There could be an in-built feature for data analysis."
"There's one thing that's a common use case, but I don't know why it's not covered in Kafka. When a message comes in, and another message with the same key arrives, the first version should be deleted automatically."
"Maybe in terms of Apache Kafka's integration with other Microsoft tools, our company faced some challenges."
"The solution is expensive."
"There are some premium connectors, for example, available in Confluent, which you cannot access in the marketplace, so there are some limitations."
"Although, specifically with Apache Kafka on Confluent Cloud, it was a bit more challenging to increase adoption because it's very expensive."
"The administration port could be more extensive."
"The clustering is a little hard for juniors and clients. It's suitable for senior engineers, but the configuration and clustering are very hard for juniors."
"The ingress issue is the main concern for me because I continue to face ingress-related issues most of the time."
"Kubernetes Everywhere is pretty good, but it can be improved in terms of reliability and speed because currently, it takes around two to three minutes to deploy my entire app, possibly due to the weight of the codes I have or some outages from the platform side."
"Due to poor planning of the application developers and resource management, I have seen crashes, downtimes, and performance issues."
"I can think of an improvement for Kubernetes Everywhere in that it should be easier to use from a developer's perspective, as it involves a lot of infrastructure numbers and DevOps."
"It only loses a small amount of points because fine-tuning network policies across very strict, air-gapped, on-premise boundaries takes extra upfront coordination during the initial discovery week."
"Regarding pricing, setup cost, and licensing, running a Kubernetes cluster can be costly depending on the use case; however, running on GCP GKE is cheaper compared to AWS, making it relatively economical in our case."
"Kubernetes Everywhere can be improved by providing an easier way for users to handle commands and developing a UI-based approach to make it easier for developers and semi-technical users, as well as focusing on improving containerization."
"Customer support for Kubernetes Everywhere could be better."
 

Pricing and Cost Advice

"I think the pricing is fair, but Confluent requires a little bit more thinking because the price can go up really quickly when it comes to premium connectors."
"Regarding pricing, Apache Kafka on Confluent Cloud is not a cheap tool. The right use case would justify the cost. It might make sense if you have a high volume of data that you can leverage to generate value for the business. But if you don't have those requirements, there are likely cheaper solutions you could use instead."
"I consider that the product's price falls under the middle range category."
Information not available
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
900,747 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
16%
Financial Services Firm
14%
Manufacturing Company
8%
Comms Service Provider
8%
Construction Company
28%
Comms Service Provider
13%
Outsourcing Company
11%
Manufacturing Company
11%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise3
Large Enterprise8
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise5
Large Enterprise8
 

Questions from the Community

What needs improvement with Apache Kafka on Confluent Cloud?
I think Apache Kafka on Confluent Cloud can be improved by probably working more around Confluent or the tool. In my opinion, it should utilize the response structures in a better way or be able to...
What is your primary use case for Apache Kafka on Confluent Cloud?
I have used Apache Kafka on Confluent Cloud for one of my projects with regard to log monitoring. My main use case for Apache Kafka on Confluent Cloud in that project was mainly streaming of the lo...
What advice do you have for others considering Apache Kafka on Confluent Cloud?
My advice to others looking into using Apache Kafka on Confluent Cloud is that it is easier and has a low learning curve. If there is any use case regarding streaming, I would suggest starting off ...
What is your experience regarding pricing and costs for Kubernetes Everywhere?
The static cost for the control plane is $75, which is not a significant issue for a large organization considering we can host multiple applications, and the cost for the nodes remains the same as...
What needs improvement with Kubernetes Everywhere?
Kubernetes Everywhere can be improved by providing an easier way for users to handle commands and developing a UI-based approach to make it easier for developers and semi-technical users, as well a...
What is your primary use case for Kubernetes Everywhere?
I have been using Kubernetes Everywhere in production and UAT for almost a year, and I have also implemented it in some of my projects for freelancing. I am using Kubernetes Everywhere for the capa...
 

Overview

Find out what your peers are saying about Databricks, Microsoft, Apache and others in Streaming Analytics. Updated: June 2026.
900,747 professionals have used our research since 2012.