Try our new research platform with insights from 80,000+ expert users

Elastic Search vs Qlik Replicate 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:
 

ROI

Sentiment score
6.4
Elastic Search offers high ROI, efficiency, and cost-effectiveness, with significant time-saving and security benefits despite some licensing costs.
Sentiment score
8.1
Qlik Replicate boosts efficiency by automating reporting, reducing costs, and accelerating data access for faster decision-making.
It is stable, and we do not encounter critical issues like server downtime, which could result in data loss.
The main benefits observed from using Elastic Search include improvements in operational efficiency, along with cost, time, and resource savings.
We have not purchased any licensed products, and our use of Elastic Search is purely open-source, contributing positively to our ROI.
I conducted a cost comparison with the AWS service provider, and this option is much cheaper than the Kinesis service offered by AWS.
Customers have seen ROI with Qlik Replicate because they get their data for analysis faster, enabling quicker decision-making compared to traditional data sourcing methods.
 

Customer Service

Sentiment score
6.5
Elastic Search's customer service is praised for responsiveness and knowledge, but complex issue support may require improvement.
Sentiment score
5.7
Qlik Replicate's support varies; clear communication helps, but users often face delays compared to more straightforward tools like HVR.
I would rate technical support from Elastic Search as three out of ten.
Even priority tickets, which should be resolved in minutes, can take days.
Support response times could be improved as there are sometimes delays in receiving replies to support cases.
 

Scalability Issues

Sentiment score
7.3
Elastic Search is scalable and integrates well, but challenges exist with large datasets and disaster recovery under rapid scaling.
Sentiment score
6.9
Qlik Replicate is scalable and flexible, benefiting medium organizations, but requires careful configuration and memory management for performance.
I would rate its scalability a ten.
I would rate the scalability of Elasticsearch as an eight.
I can actually add more storage and memory because I host it in the cloud.
The system could be scaled to include more sources and functions.
 

Stability Issues

Sentiment score
7.7
Elastic Search is stable and reliable, though version updates and data management can affect performance under stress.
Sentiment score
8.5
Qlik Replicate is stable, efficiently handles large data, and users rate its reliability highly, despite minor API concerns.
The stability of Elasticsearch was very high.
The data transfer sometimes exceeded the bandwidth limits without proper notification, which caused issues.
 

Room For Improvement

Elastic Search needs improvements in security, scalability, usability, stability, integration, support, and enhanced features for a better user experience.
Qlik Replicate needs UI improvements, clearer pricing, better performance, increased automation, enhanced support, and expanded features and marketing.
This can create problems for new developers because they have to quickly switch to another version.
The consistency and stability of Elasticsearch are commendable, and they should keep up the good work.
The architecture of Elastic Search could be improved as it is complicated for most general users to build up the environment and maintain the cluster.
It is a core-based licensing, which, especially in the banking industry, results in the system capacity being utilized up to a maximum of 60%.
Qlik Replicate could be improved in the next release by incorporating more monitoring options to monitor the logs.
 

Setup Cost

Elastic Search's free open-source version can incur back-end costs for advanced features, expertise, and premium support.
Qlik Replicate is competitively priced compared to GoldenGate, but can be costly for smaller businesses with machine capacity-based pricing.
We used the open-source version of Elasticsearch, which was free.
For Qlik Replicate, the setup cost includes the requirement of a server, which represents the hardware cost that must be covered.
Licensing is calculated based on the machine's total capacity rather than actual usage.
 

Valuable Features

Elastic Search is valued for scalability, fast indexing, powerful analysis, security features, cloud readiness, and strong community support.
Qlik Replicate efficiently transforms data in real-time, offering ease of use, comprehensive support, and seamless integration for dynamic management.
The most valuable feature of Elasticsearch was the quick search capability, allowing us to search by any criteria needed.
Elastic Search makes handling large data volumes efficient and supports complex search operations.
The full text search capabilities are particularly beneficial for handling large volumes of data.
The most valuable feature of Qlik Replicate is their change data capture feature.
Data retrieved from the system can be pushed to multiple places, supporting various divisions such as marketing, loans, and others.
 

Categories and Ranking

Elastic Search
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
71
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (9th), Search as a Service (1st), Vector Databases (3rd)
Qlik Replicate
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
18
Ranking in other categories
Data Integration (16th)
 

Featured Reviews

Anand_Kumar - PeerSpot reviewer
Captures data from all other sources and becomes a MOM aka monitoring of monitors
Scalability and ROI are the areas they have to improve. Their license terms are based on the number of cores. If you increase the number of cores, it becomes very difficult to manage at a large scale. For example, if I have a $3 million project, I won't sell it because if we're dealing with a 10 TB or 50 TB system, there are a lot of systems and applications to monitor, and I have to make an MOM (Mean of Max) for everything. This is because of the cost impact. Also, when you have horizontal scaling, it's like a multi-story building with only one elevator. You have to run around, and it's not efficient. Even the smallest task becomes difficult. That's the problem with horizontal scaling. They need to improve this because if they increase the cores and adjust the licensing accordingly, it would make more sense.
KrishnaBaddam - PeerSpot reviewer
Lightweight tool, ensures that data is replicated across different systems and simplify complex tasks such as defining relationships
Qlik Compose is something that will automate user's overall data modernization. Here data modernization includes data modeling, ETL jobs, etc. But the advantage is users can automate the overall process of data engineering and data modeling through Qlik Compose. I think that's useful when users are able to manage 60% of the workload automated. That will be very useful. That's fantastic. Replicate does not have a great AI capability. AI capabilities are present in Qlik Sense. Qlik Replicate is a very light tool. It is only meant to capture data from the log files, get the data, and transfer it, read that table structure, create the table structure, and transfer the data whenever there is a change. So, it basically integrates with the kernel of the operating system. The way it works is that these replicate tools will integrate with the kernel of the operating system, and they will access the redo log files of the database. The redo log should have access to all the files of the structure of the schema, too. So, using that technique, they redo all the data structures, create a similar structure, and replicate the structure in the target schema, table, and database. After that is done, it will start tracing the instances that are happening. For example, if data is inserted into the table, then an insert is fired on the statement on the table. So, that particular insert is captured. And based on that insert statement, it will pull the SQL query and say, "Okay, there is an insert. I need to get that data." It will get the data from the redo log itself rather than going to a database. Then, it will just pass that transaction into the target system, where it will just insert the data. And this happens instantaneously, within a microsecond. So, if there is an insert, an update, or a delete, everything is transferred immediately. It is picked from the redo log because it comes to the redo log, and then the redo log sends it to Qlik Replicate and Replicate to the target system on which Replicate is installed.
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
861,803 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Financial Services Firm
14%
Manufacturing Company
9%
Government
9%
Financial Services Firm
19%
Insurance Company
11%
Computer Software Company
10%
Manufacturing Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about ELK Elasticsearch?
Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time anal...
What is your experience regarding pricing and costs for ELK Elasticsearch?
We used the open-source version of Elasticsearch, which was free.
What needs improvement with ELK Elasticsearch?
It would be useful if a feature for renaming indices could be added without affecting the performance of other features. However, overall, the consistency and stability of Elasticsearch are already...
What do you like most about Qlik Replicate?
The main valuable feature is its real-time change data capture (CDC) capabilities, which process data with minimal latency. There is not much delay. It also performs well with batch-wise data appli...
What needs improvement with Qlik Replicate?
Qlik Replicate could be improved in the next release by incorporating more monitoring options to monitor the logs. Currently, log monitoring is not easily accessible, so there should be improvement...
What is your primary use case for Qlik Replicate?
My customer's main use case for Qlik Replicate is with one of the payment banks in India. We have implemented this Replicate project for their source data migration to cloud solutions. They wanted ...
 

Comparisons

 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
Replicate, Qlik Replicate
 

Overview

 

Sample Customers

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.
American Cancer Society, Fanzz, SM Retail, Smart Modular, Tangerine Bank, Wellcare
Find out what your peers are saying about Elastic Search vs. Qlik Replicate and other solutions. Updated: July 2025.
861,803 professionals have used our research since 2012.