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

Confluent vs Elastic Search 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

Confluent
Average Rating
8.2
Reviews Sentiment
6.3
Number of Reviews
25
Ranking in other categories
Streaming Analytics (7th)
Elastic Search
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
99
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Search as a Service (1st), Vector Databases (6th)
 

Featured Reviews

PavanManepalli - PeerSpot reviewer
AVP - Sr Middleware Messaging Integration Engineer at Wells Fargo
Has supported streaming use cases across data centers and simplifies fraud analytics with SQL-based processing
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools. They need to improve in that direction by not only reducing costs but also providing better solutions for the problems customers face to avoid frustrations, whether through future enhancement requests or ensuring product stability. The cost should be worked on, and they should provide better solutions for customers. Solutions should focus on hierarchical topics; if a customer has different types of data and sources, they should be able to send them to the same place for analytics. Currently, Confluent requires everything to send to the same topic, which becomes very large and makes running analytics difficult. The hierarchy of topics should be improved. This part is available in MQ and other products such as Solace, but it is missing in Confluent, leading many in capital markets and trading to switch to Solace. In terms of stability, it is not the stability itself that needs improvement but rather the delivery semantics. Other products offer exactly-once delivery out of the box, whereas Confluent states it will offer this but lacks the knobs or levers for tuning configurations effectively. Confluent has hundreds of configurations that application teams must understand, which creates a gap. Users are often unaware of what values to set for better performance or to achieve exactly-once semantics, making it difficult to navigate through them. Delivery semantics also need to be worked on.
reviewer2817942 - PeerSpot reviewer
Senior Software Engineer at a consultancy with 11-50 employees
Logging and vector search have transformed observability and empowered reliable ai agents
Elastic Search is not specifically being used for certain purposes. I deploy Elastic Search database on the cloud and use cloud services so that nobody can attack. However, I do not use Elastic Search to resolve attack issues. The basic main purpose of Elastic Search, as of now, I feel it can do more in the AI area. Sometime I saw that when I am developing RAG and have to generate the embeddings, which I call metadata, sometimes it tries to fail. That durability or issue handling should be improved, but apart from that, I did not find anything as of now. As per my use case, whatever I am using seems pretty good. Apart from that, some definitely improvement will be there. One improvement is that it should be faster. Whenever I am searching any logs, it takes much time. For example, if I open my log in Notepad or a similar tool, I can search the text within a second. With Elastic Search, it takes a little bit of time, ten to fifteen seconds. That can be improved. Sometimes, engineers take time to assign when I create a ticket.

Quotes from Members

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

Pros

"Kafka Connect framework is valuable for connecting to the various source systems where code doesn't need to be written."
"Having used SharePoint in the past, when I compare with traditional, old document repositories, like SharePoint, I would definitely recommend Confluent."
"One of the best features of Confluent is that it's very easy to search and have a live status with Jira."
"I would rate the scalability of the solution at eight out of ten. We have 20 people who use Confluent in our organization now, and we hope to increase usage in the future."
"The most valuable is its capability to enhance the documentation process, particularly when creating software documentation."
"The client APIs are the most valuable feature."
"The solution can handle a high volume of data because it works and scales well."
"I find Confluent's Kafka Connectors and Kafka Streams invaluable for my use cases because they simplify real-time data processing and ETL tasks by providing reliable, pre-packaged connectors and tools."
"The solution is very good with no issues or glitches."
"It's a stable solution and we have not had any issues."
"Implementing the main requirements regarding my support portal​."
"If you decide to run with it, the performance and the result can be very satisfactory."
"It helps us to analyse the logs based on the location, user, and other log parameters."
"The product is scalable with good performance."
"The best feature of Elastic Search is it does exactly what it says."
"The flexibility and the support for diverse languages that it provides for searching the database are most valuable, and we can use different languages to query the database."
 

Cons

"The formatting aspect within the page can be improved and more powerful."
"There is no local support team in Saudi Arabia."
"They should remove Zookeeper because of security issues."
"The solution could have an extra plugin or upgrading feature. In addition, it could have more integration with different platforms and be more compatible."
"It could be improved by including a feature that automatically creates a new topic and puts failed messages."
"Confluent's price needs improvement."
"I am not very impressed by Confluent. We continuously face issues, such as Kafka being down and slow responses from the support team."
"There is a limitation when it comes to seamlessly importing Microsoft documents into Confluent pages, which can be inconvenient for users who frequently work with Microsoft Office tools and need to transition their content to Confluent."
"The reports could improve."
"There is another solution I'm testing which has a 500 record limit when you do a search on Elastic Enterprise Search."
"Performance improvement could come from skipping background refresh on search idle shards (which is already being addressed in the upcoming seventh version)."
"The setup is somewhat complicated due to multiple dependencies and relations with different systems."
"The one area that can use improvement is the automapping of fields."
"There are some features lacking in ELK Elasticsearch."
"Elasticsearch is useful for different business processes, but there are some problems."
"Its licensing needs to be improved. They don't offer a perpetual license. They want to know how many nodes you will be using, and they ask for an annual subscription. Otherwise, they don't give you permission to use it. Our customers are generally military or police departments or customers without connection to the internet. Therefore, this model is not suitable for us. This subscription-based model is not the best for OEM vendors. Another annoying thing about Elasticsearch is its roadmap. We are developing something, and then they say, "Okay. We have removed that feature in this release," and when we are adapting to that release, they say, "Okay. We have removed that one as well." We don't know what they will remove in the next version. They are not looking for backward compatibility from the customers' perspective. They just remove a feature and say, "Okay. We've removed this one." In terms of new features, it should have an ODBC driver so that you can search and integrate this product with existing BI tools and reporting tools. Currently, you need to go for third parties, such as CData, in order to achieve this. ODBC driver is the most important feature required. Its Community Edition does not have security features. For example, you cannot authenticate with a username and password. It should have security features. They might have put it in the latest release."
 

Pricing and Cost Advice

"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"On a scale from one to ten, where one is low pricing and ten is high pricing, I would rate Confluent's pricing at five. I have not encountered any additional costs."
"The pricing model of Confluent could improve because if you have a classic use case where you're going to use all the features there is no plan to reduce the features. You should be able to pick and choose basic services at a reduced price. The pricing was high for our needs. We should not have to pay for features we do not use."
"It comes with a high cost."
"Regarding pricing, I think Confluent is a premium product, but it's hard for me to say definitively if it's overly expensive. We're still trying to understand if the features and reduced maintenance complexity justify the cost, especially as we scale our platform use."
"You have to pay additional for one or two features."
"The solution is cheaper than other products."
"Confluent is an expensive solution."
"The basic license is free, but it comes with a lot of features that aren't free. With a gold license, we get active directory integration. With a platinum license, we get alerting."
"We are using the open-sourced version."
"The solution is free."
"The cost varies based on factors like usage volume, network load, data storage size, and service utilization. If your usage isn't too extensive, the cost will be lower."
"There is a free version, and there is also a hosted version for which you have to pay. We're currently using the free version. If things go well, we might go for the paid version."
"This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic."
"The premium license is expensive."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
902,988 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Retailer
11%
Computer Software Company
8%
Manufacturing Company
6%
Financial Services Firm
12%
Manufacturing Company
9%
Computer Software Company
8%
Retailer
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise17
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise12
Large Enterprise49
 

Questions from the Community

What is your experience regarding pricing and costs for Confluent?
They charge a lot for scaling, which makes it expensive.
What needs improvement with Confluent?
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about ...
What is your primary use case for Confluent?
The main use cases for Confluent are log aggregation and streaming. I'm familiar with Confluent stream processing with KSQL. KSQL helps in terms of data analytics strategies because if we are the d...
What is your experience regarding pricing and costs for ELK Elasticsearch?
Elastic Search is easy to use in Azure cloud. Mostly, my full company uses Azure cloud, so it is easy to use. Cost-wise, my company found Elastic Search is good. Cost matters. Based on cost and use...
What needs improvement with ELK Elasticsearch?
The initial configuration could be easier; at first, the learning curve is a little high, and over time, it becomes easier. For me, the initial configuration might be improved.
What is your primary use case for ELK Elasticsearch?
We use Elastic Search for a research application based on paper study, and the primary usage is for indexing the data and then functioning in a similar way to an e-commerce search bar.
 

Comparisons

 

Also Known As

No data available
Elastic Enterprise Search, Swiftype, Elastic Cloud
 

Overview

 

Sample Customers

ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
T-Mobile, Adobe, Booking.com, BMW, Telegraph Media Group, Cisco, Karbon, Deezer, NORBr, Labelbox, Fingerprint, Relativity, NHS Hospital, Met Office, Proximus, Go1, Mentat, Bluestone Analytics, Humanz, Hutch, Auchan, Sitecore, Linklaters, Socren, Infotrack, Pfizer, Engadget, Airbus, Grab, Vimeo, Ticketmaster, Asana, Twilio, Blizzard, Comcast, RWE and many others.
Find out what your peers are saying about Amazon Web Services (AWS), Informatica, Palantir and others in Cloud Data Integration. Updated: June 2026.
902,988 professionals have used our research since 2012.