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

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 (6th)
Qlik Replicate
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
18
Ranking in other categories
Data Integration (24th)
 

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.6%, down 8.2% compared to last year.
Qlik Replicate, on the other hand, focuses on Data Integration, holds 1.4% mindshare, down 3.0% since last year.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Confluent6.6%
Apache Flink8.9%
Databricks8.1%
Other76.4%
Streaming Analytics
Data Integration Mindshare Distribution
ProductMindshare (%)
Qlik Replicate1.4%
SSIS3.7%
Informatica Intelligent Data Management Cloud (IDMC)3.6%
Other91.3%
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

"A person with a good IT background and HTML will not have any trouble with Confluent."
"As an enterprise organization, data availability is critical and Confluent provides that SLA support."
"The solution can handle a high volume of data because it works and scales well."
"Implementing Confluent's schema registry has significantly enhanced our organization's data quality assurance."
"Our main goal is to validate whether we can build a scalable and cost-efficient way to replicate data from these various sources."
"We mostly use the solution's message queues and event-driven architecture."
"To date, we have seen improvements in performance and scalability, so we recommend this solution."
"We primarily use Confluent for service desk and task management, and it is also good for knowledge base management."
"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."
"We use Qlik Replicate to change data capture of databases in production environments."
"Its capability to replicate the data without impacting the source databases performance-wise is the most useful aspect."
"Support has been great."
"From a technical perspective, this is an excellent product."
"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 applications."
"From a technical perspective, this is an excellent product."
 

Cons

"Recently, there has been a lot of buzz about Confluent charging high fees while not offering features that match those of other tools."
"The formatting aspect within the page can be improved and more powerful."
"The solution could have an extra plugin or upgrading feature. In addition, it could have more integration with different platforms and be more compatible."
"The pricing model should include the ability to pick features and be charged for them only."
"The beginner who doesn't know how to work on HTML will struggle as when you create spaces in the Confluent, if you want to have some meeting notes or anything else, you need to know HTML and which HTML tags to include."
"The product should integrate tools for incorporating diagrams like Lucidchart. It also needs to improve its formatting features. We also faced issues while granting permissions."
"It would be great if the knowledge based documents in the support portal could be available for public use as well."
"They should remove Zookeeper because of security issues."
"We would like to see more details in messages about errors with the system."
"Support for this product could be better. When we do, my rating is a two out of five, because their internal support is not great."
"Some features on the graphical user interface are clunky."
"Support response times could be improved as there are sometimes delays in receiving replies to support cases."
"The product should improve its licensing limitation."
"Support-wise, this solution is in need of improvement."
"This product could be improved by providing more insight regarding errors. We tried to debug it, but we could not trace the error message."
"Some features can also be overly dependent on each other. So, there is room for improvement."
 

Pricing and Cost Advice

"It comes with a high cost."
"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."
"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."
"Confluent is highly priced."
"The solution is cheaper than other products."
"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."
"You have to pay additional for one or two features."
"Qlik Replicate is mainly suited for large companies. However, it is too costly for small businesses. Its pricing is high."
"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."
"Overall, Qlik is an expensive solution. You need to pay for all additional features that you would like to use."
"Qlik Replicate is not expensive, compared to GoldenGate."
"Unlike Azure, where you pay based on consumption, Qlik Replicate seems to charge per endpoint."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
892,611 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Retailer
11%
Computer Software Company
10%
Manufacturing Company
5%
Financial Services Firm
16%
Manufacturing Company
10%
Insurance Company
10%
Computer Software Company
7%
 

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 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 is your primary use case for Confluent?
The main use cases for Confluent are log aggregation and streaming. I'm familiar with Confluent stream processing with KSQL. KSQL helps in terms of data analytics strategies because if we are the d...
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: April 2026.
892,611 professionals have used our research since 2012.