We performed a comparison between Confluent and Elastic Search based on real PeerSpot user reviews.
Find out in this report how the two Cloud Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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."
"A person with a good IT background and HTML will not have any trouble with Confluent."
"The solution can handle a high volume of data because it works and scales well."
"The monitoring module is impressive."
"The most valuable feature of Confluent is the wide range of features provided. They're leading the market in this category."
"The documentation process is fast with the tool."
"Implementing Confluent's schema registry has significantly enhanced our organization's data quality assurance."
"The most valuable feature that we are using is the data replication between the data centers allowing us to configure a disaster recovery or software. However, is it's not mandatory to use and because most of the features that we use are from Apache Kafka, such as end-to-end encryption. Internally, we can develop our own kind of product or service from Apache Kafka."
"I like how it allows us to connect to Kafka and get this data in a document format very easily. Elasticsearch is very fast when you do text-based searches of documents. That area is very good, and the search is very good."
"The products comes with REST APIs."
"The initial installation and setup were straightforward."
"The most valuable feature of Elastic Enterprise Search is user behavior analysis."
"The most valuable feature of Elastic Enterprise Search is the Discovery option for the visualization of logs on a GPU instead of on the server."
"The flexibility and the support for diverse languages that it provides for searching the database are most valuable. We can use different languages to query the database."
"Data indexing of historical data is the most beneficial feature of the product."
"There's lots of processing power. You can actually just add machines to get more performance if you need to. It's pretty flexible and very easy to add another log. It's not like 'oh, no, it's going to be so much extra data'. That's not a problem for the machine. It can handle it."
"Currently, in the early stages, I see a gap on the security side. If you are using the SaaS version, we would like to get a fuller, more secure solution that can be adopted right out of the box. Confluence could do a better job sharing best practices or a reusable pattern that others have used, especially for companies that can not afford to hire professional services from Confluent."
"It would help if the knowledge based documents in the support portal could be available for public use as well."
"Confluent's price needs improvement."
"It could be improved by including a feature that automatically creates a new topic and puts failed messages."
"The product should integrate tools for incorporating diagrams like Lucidchart. It also needs to improve its formatting features. We also faced issues while granting permissions."
"there is room for improvement in the visualization."
"There is no local support team in Saudi Arabia."
"The formatting aspect within the page can be improved and more powerful."
"We see the need for some improvements with Elasticsearch. We would like the Elasticsearch package to include training lessons for our staff."
"It should be easier to use. It has been getting better because many functions are pre-defined, but it still needs improvement."
"There is another solution I'm testing which has a 500 record limit when you do a search on Elastic Enterprise Search. That's the only area in which I'm not sure whether it's a limitation on our end in terms of knowledge or a technical limitation from Elastic Enterprise Search. There is another solution we are looking at that rides on Elastic Enterprise Search. And the limit is for any sort of records that you're doing or data analysis you're trying to do, you can only extract 500 records at a time. I know the open-source nature has a lot of limitations, Otherwise, Elastic Enterprise Search is a fantastic solution and I'd recommend it to anyone."
"They're making changes in their architecture too frequently."
"It is hard to learn and understand because it is a very big platform. This is the main reason why we still have nothing in production. We have to learn some things before we get there."
"There are some features lacking in ELK Elasticsearch."
"Dashboards could be more flexible, and it would be nice to provide more drill-down capabilities."
"I have not been using the solution for many years to know exactly the improvements needed. However, they could simplify how the YML files have to be structured properly."
Confluent is ranked 4th in Streaming Analytics with 19 reviews while Elastic Search is ranked 9th in Cloud Data Integration with 59 reviews. Confluent is rated 8.4, while Elastic Search is rated 8.2. The top reviewer of Confluent writes "Has good technical support services and a valuable feature for real-time data streaming ". On the other hand, the top reviewer of Elastic Search writes "Played a crucial role in enhancing our cybersecurity efforts ". Confluent is most compared with Amazon MSK, Amazon Kinesis, Databricks, AWS Glue and Oracle GoldenGate, whereas Elastic Search is most compared with Faiss, Milvus, Pinecone, Azure Search and Amazon Kendra. See our Confluent vs. Elastic Search report.
See our list of best Cloud Data Integration vendors.
We monitor all Cloud Data Integration 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.
