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.3
Number of Reviews
25
Ranking in other categories
Streaming Analytics (5th)
Qlik Replicate
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
19
Ranking in other categories
Data Integration (19th)
 

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 6.8%, down 8.5% compared to last year.
Qlik Replicate, on the other hand, focuses on Data Integration, holds 1.6% mindshare, down 3.1% since last year.
Streaming Analytics Market Share Distribution
ProductMarket Share (%)
Confluent6.8%
Apache Flink11.3%
Databricks9.5%
Other72.4%
Streaming Analytics
Data Integration Market Share Distribution
ProductMarket Share (%)
Qlik Replicate1.6%
SSIS3.7%
Informatica Intelligent Data Management Cloud (IDMC)3.5%
Other91.2%
Data Integration
 

Featured Reviews

PavanManepalli - PeerSpot reviewer
AVP - Sr Middleware Messaging Integration Engineer at Wells Fargo
Has supported streaming use cases across data centers and simplifies fraud analytics with SQL-based processing
I recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools. They need to improve in that direction by not only reducing costs but also providing better solutions for the problems customers face to avoid frustrations, whether through future enhancement requests or ensuring product stability. The cost should be worked on, and they should provide better solutions for customers. Solutions should focus on hierarchical topics; if a customer has different types of data and sources, they should be able to send them to the same place for analytics. Currently, Confluent requires everything to send to the same topic, which becomes very large and makes running analytics difficult. The hierarchy of topics should be improved. This part is available in MQ and other products such as Solace, but it is missing in Confluent, leading many in capital markets and trading to switch to Solace. In terms of stability, it is not the stability itself that needs improvement but rather the delivery semantics. Other products offer exactly-once delivery out of the box, whereas Confluent states it will offer this but lacks the knobs or levers for tuning configurations effectively. Confluent has hundreds of configurations that application teams must understand, which creates a gap. Users are often unaware of what values to set for better performance or to achieve exactly-once semantics, making it difficult to navigate through them. Delivery semantics also need to be worked on.
SW
Solution Architect at Predoole Analytics
Real-time data synchronization faces challenges with monitoring and affordability
The user-friendly interface in Qlik Replicate simplifies configuration and management of replication tasks because it is based on GUI, and users don't have to write any scripts. It is entirely drag and drop functionality. Even with zero knowledge of scripting, users can effectively use Qlik Replicate. The most valuable feature of Qlik Replicate is their change data capture feature. As soon as data is entered into the source, it gets captured at target locations. This occurs in near real-time, with replication happening within seconds at the target location. Additionally, whatever operations are performed at the source, whether adding data, deleting data, or updating anything, it gets replicated at target locations. It functions as data injection from source to target, ensuring all operations performed on the source system are replicated on target systems.

Quotes from Members

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

Pros

"The biggest benefit of Confluent as a tool is that it is a distributed platform that provides more durability and stability."
"The features I find most useful in Confluent are the Multi-Region Cluster, MRC, and the Cluster Linking for replication."
"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."
"One of the best features of Confluent is that it's very easy to search and have a live status with Jira."
"The documentation process is fast with the tool."
"The solution can handle a high volume of data because it works and scales well."
"Our main goal is to validate whether we can build a scalable and cost-efficient way to replicate data from these various sources."
"The client APIs are the most valuable feature."
"From a technical perspective, this is an excellent product."
"The most valuable features of Qlik Replicate are its CDC performance and trigger functions. CDC feature is important to the financial industry."
"Low-priced reporting and analytics solution, with good scalability and stability. It has on-premises and cloud versions that are cohesive and can integrate well."
"Qlik Replicate's ability to correctly map and replicate data, especially when converting complex fields like packed decimal fields into integers, stands out."
"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 system is basically user-driven, mostly operating as a local platform."
"The CDC and the flexibility to use QVD as a source are the most valuable features of Qlik Replicate."
"Qlik Replicate's real-time data delivery significantly impacts our organization's data insights, especially concerning network outages."
 

Cons

"Confluent has a good monitoring tool, but it's not customizable."
"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."
"Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools."
"In Confluent, there could be a few more VPN options."
"Areas for improvement include implementing multi-storage support to differentiate between database stores based on data age and optimizing storage costs."
"Confluent's price needs improvement."
"We continuously face issues, such as Kafka being down and slow responses from the support team."
"The formatting aspect within the page can be improved and more powerful."
"In terms of handling diverse data sources, Qlik Replicate does exhibit certain shortcomings."
"The UI and data version control can be improved."
"We'd like better connectivity."
"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 various scenarios, an important consideration is when we encounter issues and Qlik Replicate suggests reloading a specific table. If we face any problems or encounter errors with that table, it becomes necessary to make a change in Qlik Replicate. Performing a full reload every time is not feasible or practical. Instead, we should identify the specific issues and address them without repeating the entire reloading process. Based on this approach, we can investigate and resolve the problem by performing targeted loads from the source itself. This change aligns with my perspective and is something I would like to implement."
"In the next release, I would like to see closer integration with data catalyst."
"There is complexity involved in the licensing part of this system."
"Support for this product is not great. It needs to be improved."
 

Pricing and Cost Advice

"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"It comes with a high cost."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"Regarding pricing, I think Confluent is a premium product, but it's hard for me to say definitively if it's overly expensive. We're still trying to understand if the features and reduced maintenance complexity justify the cost, especially as we scale our platform use."
"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."
"Confluent is an expensive solution."
"Confluent is highly priced."
"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."
"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."
"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.
882,333 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Computer Software Company
11%
Retailer
9%
Manufacturing Company
6%
Financial Services Firm
16%
Manufacturing Company
10%
Insurance Company
10%
Computer Software Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise16
By reviewers
Company SizeCount
Small Business9
Large Enterprise11
 

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 recommend that Confluent should improve its solution to keep up with competitors in the market, such as Solace and other upcoming tools such as NATS. Recently, there has been a lot of buzz about ...
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?
In terms of handling diverse data sources, Qlik Replicate does exhibit certain shortcomings.Other areas of Qlik Replicate that could be improved include its ability to serve as a single point tool,...
What is your primary use case for Qlik Replicate?
My usual use cases for Qlik Replicate involve my previous organization and my current organization. I can provide my current experience. As an Australian energy provider, we have a lot of operation...
 

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: February 2026.
882,333 professionals have used our research since 2012.