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

Confluent 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:
 

Categories and Ranking

Confluent
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
23
Ranking in other categories
Streaming Analytics (3rd)
Qlik Replicate
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
18
Ranking in other categories
Data Integration (16th)
 

Mindshare comparison

Confluent and Qlik Replicate aren’t in the same category and serve different purposes. Confluent is designed for Streaming Analytics and holds a mindshare of 8.3%, down 10.2% compared to last year.
Qlik Replicate, on the other hand, focuses on Data Integration, holds 3.0% mindshare, up 2.9% since last year.
Streaming Analytics
Data Integration
 

Featured Reviews

Gustavo-Barbosa Dos Santos - PeerSpot reviewer
Has good technical support services and a valuable feature for real-time data streaming
Implementing Confluent's schema registry has significantly enhanced our organization's data quality assurance. It helps us understand the various requirements of multiple customers and validates the information for different versions. We can automate the tasks using Confluent Kafka. Thus, it guarantees us the data quality and maintains the integrity of message contracts.
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.

Quotes from Members

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

Pros

"The documentation process is fast with the tool."
"We ensure seamless management of Kafka through Confluent, allowing all of our Kafka activities to be handled by a third party."
"The most valuable feature of Confluent is the wide range of features provided. They're leading the market in this category."
"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."
"A person with a good IT background and HTML will not have any trouble with Confluent."
"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."
"Kafka Connect framework is valuable for connecting to the various source systems where code doesn't need to be written."
"With Confluent Cloud we no longer need to handle the infrastructure and the plumbing, which is a concern for Confluent. The other advantage is that all portfolios have access to the data that is being shared."
"The system is basically user-driven, mostly operating as a local platform."
"Qlik Replicate's ability to correctly map and replicate data, especially when converting complex fields like packed decimal fields into integers, stands out."
"A valuable feature of Qlik Replicate is that you do not need ETL. It's easy to use—you choose two systems and it automatically replicates them. Even if there is no CDC available, if you insert it and update it, and there is nothing to find out, then you can use Qlik Replicate. It's a good product."
"The cost is under control with this solution, unlike other services where it's not."
"The most useful functions of Qlik Replicate are the data manipulation to transformations."
"We use Qlik Replicate to change data capture of databases in production environments."
"Qlik Replicate stands out with its cutting-edge technology and its ability to handle diverse data management tasks. This powerful tool allows us to efficiently and swiftly load data into various data stores or destinations, while also enabling easy distribution across different endpoints. A notable feature is its capability to reload data from multiple sources by creating multiple tasks within a brief timeframe of fifteen to twenty minutes. This eliminates the need for manual intervention and ensures quick data loading from different tables."
"The most valuable feature of Qlik Replicate is their change data capture feature."
 

Cons

"In Confluent, there could be a few more VPN options."
"Confluent's price needs improvement."
"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."
"The pricing model should include the ability to pick features and be charged for them only."
"It could be improved by including a feature that automatically creates a new topic and puts failed messages."
"It could have more integration with different platforms."
"One area we've identified that could be improved is the governance and access control to the Kafka topics. We've found some limitations, like a threshold of 10,000 rules per cluster, that make it challenging to manage access at scale if we have many different data sources."
"It requires some application specific connectors which are lacking. This needs to be added."
"This product could be improved by providing more insight regarding errors. One of our customers that uses Qlik Replicate has had an issue. We tried to debug it, but we could not trace the error message. The infrastructure site should give us more insight about errors. Qlik Replicate is not a business solution, it's an IT solution. The reporting tools and bug site should be improved."
"The solution's flexibility to work with APIs should also be improved since it is very weak in working with APIs."
"Support for this product is not great. It needs to be improved."
"We'd like better connectivity."
"There is complexity involved in the licensing part of this system."
"The disadvantage is people are not going for this license because it is not marketed properly."
"I am not very comfortable with Qlik support as it often goes in loops. Even priority tickets, which should be resolved in minutes, can take days."
"In the next release, I would like to see closer integration with data catalyst."
 

Pricing and Cost Advice

"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
"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."
"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."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"You have to pay additional for one or two features."
"The solution is cheaper than other products."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"It comes with a high cost."
"Pricing for this solution is very reasonable."
"Unlike Azure, where you pay based on consumption, Qlik Replicate seems to charge per endpoint."
"Qlik Replicate is mainly suited for large companies. However, it is too costly for small businesses. Its pricing is high."
"Qlik Replicate is not expensive, compared to GoldenGate."
"On a scale from one to ten, where one is cheap, and ten is expensive, I rate Qlik Replicate's pricing a nine out of ten."
"Overall, Qlik is an expensive solution. You need to pay for all additional features that you would like to use."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
865,295 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
15%
Manufacturing Company
6%
Retailer
5%
Financial Services Firm
18%
Insurance Company
11%
Manufacturing Company
9%
Computer Software Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Confluent?
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 to...
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 am not very impressed by Confluent. We continuously face issues, such as Kafka being down and slow responses from the support team. The lack of easy access to the Confluent support team is also a...
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

No data available
Replicate, Qlik Replicate
 

Overview

 

Sample Customers

ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
American Cancer Society, Fanzz, SM Retail, Smart Modular, Tangerine Bank, Wellcare
Find out what your peers are saying about Confluent vs. Qlik Replicate and other solutions. Updated: July 2025.
865,295 professionals have used our research since 2012.