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

CloverETL 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

CloverETL
Average Rating
7.0
Reviews Sentiment
6.8
Number of Reviews
2
Ranking in other categories
Data Integration (58th), Data Visualization (35th)
Elastic Search
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
100
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Search as a Service (1st), Vector Databases (6th)
 

Featured Reviews

it_user856614 - PeerSpot reviewer
Lead Programmer at a healthcare company with 10,001+ employees
Very easy to schedule jobs and monitor them, however we run out heap space even with a high allocation
Flexibility: We can bring in data from multiple sources, e.g., databases, text files, JSON, email, XML, etc. This has been very helpful Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility. Server features for scheduler: It is…
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

"Key features include wealth of pre-defined components; all components are customizable; descriptive logging, especially for error messages."
"Server features for scheduler: It is very easy to schedule jobs and monitor them. The interface is easy to use."
"We switched to CloverETL because of its flexibility to connect to various data sources and no dependence on native language and ease of use."
"No dependence on native language and ease of use.​​"
"Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility."
"Familiar, intuitive GUI coming from a Java development background, in-depth, descriptive, and well-laid-out documentation, responsive support through forums directly from Clover staff, a wealth of customizable pre-defined components, descriptive logging for error messages, and ease of install with a light footprint make it very effective to use."
"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."
"The ability to aggregate log and machine data into a searchable index reduces time to identify and isolate issues for an application. Saves time in triage and incident response by eliminating manual steps to access and parse logs on separate systems, within large infrastructure footprints."
"The best feature of Elastic Search that I appreciate is its monitoring capability."
"The most valuable features of Elastic Enterprise Search are it's cloud-ready and we do a lot of infrastructure as code. By using ELK, we're able to deploy the solution as part of our ISC deployment."
"From the customer side, Elastic Search is super fast and very efficient, delivering results quickly."
"The solution is quite scalable and this is one of its advantages."
"ELK being an open source certainly provided a platform for our organization to get involved."
"I appreciate the indexing capabilities and the speed of indexing in their product, which demonstrates how quickly logs are collected and stored."
 

Cons

"​Resource management: We typically run out of heap space, and even the allocation of high heap space does not seem to be enough.​"
"Its documentation could be improved.​"
"Needs easier automated failure recovery, more and more intuitive auto-generated or filled-in code for components, and easier or more automated sync between CloverETL Designer and CloverETL Server."
"The most significant issue I find with Elastic Search is that it gets out of sync, and this has happened in both cases where I have implemented it."
"Improving machine learning capabilities would be beneficial."
"Elastic Enterprise Search could improve its SSL integration easier. We should not need to go to the back-end servers to do configuration, we should be able to do it on the GUI."
"Elastic Enterprise Search's tech support is good but it could be improved."
"Maybe Elastic Search could improve the analytics part of the search so it can be more powerful to the user."
"There should be more stability."
"We'd like more user-friendly integrations."
"This product could be improved with additional security, and the addition of support for machine learning devices."
 

Pricing and Cost Advice

Information not available
"The premium license is expensive."
"The solution is not expensive because users have the option of choosing the managed or the subscription model."
"The version of Elastic Enterprise Search I am using is open source which is free. The pricing model should improve for the enterprise version because it is very expensive."
"We are using the open-sourced version."
"ELK has been considered as an alternative to Splunk to reduce licensing costs."
"The price of Elastic Enterprise is very, very competitive."
"To access all the features available you require both the open source license and the production license."
"​The pricing and license model are clear: node-based model."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
909,948 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
26%
Manufacturing Company
12%
Comms Service Provider
9%
Computer Software Company
9%
Financial Services Firm
11%
Manufacturing Company
9%
Computer Software Company
7%
Outsourcing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise12
Large Enterprise50
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for ELK Elasticsearch?
The pricing for Elastic Search is mainly budgeted according to the organization budget, so we take it as a yearly subscription, and that is acceptable since we do get a fair discount when we are ta...
What needs improvement with ELK Elasticsearch?
When we get the logs, it is mostly about how we edit the configurations and how we make changes according to the requirements of our organization. In these cases, the logs sometimes can be a bit in...
What is your primary use case for ELK Elasticsearch?
I am the Elastic Search admin for my organization, and we are using Elastic Search to handle the traffic to GCP. The monitoring of all the clusters and all the deployments are quite good, and compa...
 

Comparisons

 

Also Known As

No data available
Elastic Enterprise Search, Swiftype, Elastic Cloud
 

Overview

 

Sample Customers

IBM, Oracle, MuleSoft, GoodData, Thomson Reuters, salesforce.com, Comcast, Active Network, SHOP.CA
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: August 2026.
909,948 professionals have used our research since 2012.