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.
reviewer2774796 - PeerSpot reviewer
Data Governance System Specialist at a energy/utilities company with 5,001-10,000 employees
Real-time outage insights have improved customer communication but data source support needs work
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, similar to Databricks and Azure Data Lake, depending on the kind of capabilities required. I believe that having updated documentation is crucial as we encountered a scenario while going through documentation that had not been updated since 2024, which introduced risks since we rely on accurate documentation for task imports and endpoint re-credentialing considerations before reaching out to customer support. Additionally, functionalities for running standardized data quality rules and validation logic, along with exception monitoring similar to what is available in Databricks, would be beneficial for users. While Qlik Replicate is scalable, I find there are limitations. When deploying a tool, it can be centralized, decentralized, or federated, depending on the organization's control and responsibility preferences. We successfully scaled several of our Oracle RDBMS systems simultaneously, including PeopleSoft HR and our network access request systems. However, addressing the shortcomings we discussed would enhance its competitiveness in the market.

Quotes from Members

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

Pros

"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 client APIs are the most valuable feature."
"Kafka Connect framework is valuable for connecting to the various source systems where code doesn't need to be written."
"The benefit is escaping email communication. Sometimes people ignore emails or put them into spam, but with Confluence, everyone sees the same text at the same time."
"The most valuable is its capability to enhance the documentation process, particularly when creating software documentation."
"Some of the best features are that it's very quick to set up, very easy to have a centralized area that gives us a history of changes, and the ability to give feedback on any information placed onto the pages."
"The monitoring module is impressive."
"One of the best features of Confluent is that it's very easy to search and have a live status with Jira."
"The most useful functions of Qlik Replicate are the data manipulation to transformations."
"The system is basically user-driven, mostly operating as a local platform."
"A pretty good series of connectors is one of the best features of Qlik Replicate."
"The most valuable features of Qlik Replicate are its CDC performance and trigger functions. CDC feature is important to the financial industry."
"The cost is under control with this solution, unlike other services where it's not."
"It enables us to transform data at the latest stage rather than in ETL loads, so it's more ELT which is one of the advantages. It is also in near real-time, which brings significant advantage for our embedded analytics approach."
"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."
"Qlik Replicate's ability to correctly map and replicate data, especially when converting complex fields like packed decimal fields into integers, stands out."
 

Cons

"Areas for improvement include implementing multi-storage support to differentiate between database stores based on data age and optimizing storage costs."
"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."
"There is a limitation when it comes to seamlessly importing Microsoft documents into Confluent pages, which can be inconvenient for users who frequently work with Microsoft Office tools and need to transition their content to Confluent."
"Confluence could improve the server version of the solution. However, most companies are going to the cloud."
"They should remove Zookeeper because of security issues."
"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."
"It would be better if the solution’s pricing were more obvious."
"The UI and data version control can be improved."
"When you remote into it the Qlik Replicate UI a lot of times it just freezes. We set up the EC2, to allow them to go to the server and click on the Replicate icon, it just opens up and just sits there. At that point, we have to go into the EC2 and then reboot the server. This should be fixed, it is frustrating."
"Support response times could be improved as there are sometimes delays in receiving replies to support cases."
"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."
"We would like to see more details in messages about errors with the system."
"Some features on the graphical user interface are clunky."
"The solution's flexibility to work with APIs should also be improved since it is very weak in working with APIs."
 

Pricing and Cost Advice

"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."
"Confluence's pricing is quite reasonable, with a cost of around $10 per user that decreases as the number of users increases. Additionally, it's worth noting that for teams of up to 10 users, the solution is completely free."
"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 has a yearly license, which is a bit high because it's on a per-user basis."
"It comes with a high cost."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"The solution is cheaper than other products."
"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 not expensive, compared to GoldenGate."
"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."
"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,103 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,103 professionals have used our research since 2012.