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

CloverETL vs Elastic Search comparison

Why PeerSpot?
 

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 (61st), Data Visualization (34th)
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 (6th), 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

"Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility."
"Server features for scheduler: It is very easy to schedule jobs and monitor them. The interface is easy to use."
"Key features include wealth of pre-defined components; all components are customizable; descriptive logging, especially for error messages."
"No dependence on native language and ease of use.​​"
"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."
"We switched to CloverETL because of its flexibility to connect to various data sources and no dependence on native language and ease of use."
"The most valuable feature for us is the analytics that we can configure and view using Kibana."
"The most valuable feature of the solution is its utility and usefulness."
"The solution has a lot of features; they have machine learning jobs they can implement, I'm not there yet, but I can use anomaly detection to see there are various processes that can find users that aren't supposed to log onto certain machines."
"I appreciate the indexing capabilities and the speed of indexing in their product, which demonstrates how quickly logs are collected and stored."
"The AI-based attribute tagging is a valuable feature."
"We have many advantages from the features of Elasticsearch, and we have enough possibilities and features with Elasticsearch for our business requirements."
"A good use case is saving metadata of your systems for data cataloging. Various systems, like those opened in metadata and similar applications, use Elasticsearch to store their text data."
"It gives us the possibility to store and query this data and also do this efficiently and securely and without delays."
 

Cons

"Its documentation could be improved.​"
"​Resource management: We typically run out of heap space, and even the allocation of high heap space does not seem to be enough.​"
"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."
"I would like to see more open source tools and testing as well as a signature analysis in the solution."
"Machine learning on search needs improvement."
"The metadata gets stored along with indexes and isn't queryable."
"They could simplify the Filebeat and Logstash configuration piece. There are a lot of manual steps on the operating system."
"There should be more stability."
"Scalability and ROI are the areas they have to improve."
"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."
"I found an issue with Elasticsearch in terms of aggregation. They are good, yet the rules written for this are not really good."
 

Pricing and Cost Advice

Information not available
"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."
"The solution is less expensive than Stackdriver and Grafana."
"We are using the open-sourced version."
"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 free version and intend to upgrade."
"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 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."
"The price of Elastic Enterprise is very, very competitive."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
26%
Manufacturing Company
13%
Comms Service Provider
13%
Computer Software Company
7%
Financial Services Firm
11%
Manufacturing Company
9%
Outsourcing Company
9%
Comms Service Provider
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...
 

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: September 2026.
915,341 professionals have used our research since 2012.