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

Confluent vs WhereScape RED 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)
WhereScape RED
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
15
Ranking in other categories
Data Integration (42nd)
 

Mindshare comparison

Confluent and WhereScape RED 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.
WhereScape RED, on the other hand, focuses on Data Integration, holds 1.3% mindshare, up 1.1% since last year.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Confluent6.6%
Apache Flink8.9%
Databricks8.1%
Other76.4%
Streaming Analytics
Data Integration Mindshare Distribution
ProductMindshare (%)
WhereScape RED1.3%
SSIS3.7%
Informatica Intelligent Data Management Cloud (IDMC)3.6%
Other91.4%
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.
reviewer1618884 - PeerSpot reviewer
BI Analyst DW Architect at a mining and metals company with 10,001+ employees
Quick to set up, flexible, and stable
The scheduling part I don't like due to the fact that it allows you to schedule as a parent and child and other things, however, the error trackability has to be a little more user-friendly. It's also not user-friendly in the sense that it loads all the jobs and there are not enough filters so that it doesn't need to load everything. If the job fails, you don't get any type of alert or email. It would be ideal if there was some sort of automated alert message. Technical support isn't the best. It would be ideal if we understood how to do it in a card exception regarding exclusion, where the card is captured separately rather than filling the whole process on the data inbound side. Certain workloads like this are organized in such a way where you seem to be doubling the work as opposed to streamlining the process.

Quotes from Members

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

Pros

"We mostly use the solution's message queues and event-driven architecture."
"The client APIs are the most valuable feature."
"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."
"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."
"To date, we have seen improvements in performance and scalability, so we recommend this solution."
"Our main goal is to validate whether we can build a scalable and cost-efficient way to replicate data from these various sources."
"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."
"RED has provided us the ability to integrate, stage, and transform data from diverse sources into an enterprise-grade data warehouse which meets the needs of my organization, but it also enables us to easily and quickly make ETL or DW changes."
"Speed to market of a warehouse solution at a relatively inexpensive price point."
"The most valuable feature is the metadata generated code and data structures and that it is a fully integrated environment."
"WhereScape RED has improved our business's ability to generate needed reporting without requiring a large team of developers to manually code all of the necessary plumbing."
"I like the data vault implementations, the ELT feature, and the automatic generation of logic as it saves time."
"WhereScape is really helpful in terms of architecture data. Everything is one of automation. Two people can do thousands of tables in one day or two. It saves a lot of time."
"During the POC myself and one WS resource were able to deliver a project in 3 days that had been in development by other resources for 6 months and still hadn't been delivered."
"The product takes on much of the painful, time-consuming, manual and repetitive tasks, allowing you to focus on meeting business requirements."
 

Cons

"Confluence could improve the server version of the solution. However, most companies are going to the cloud."
"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 could be improved by including a feature that automatically creates a new topic and puts failed messages."
"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."
"The solution could have an extra plugin or upgrading feature. In addition, it could have more integration with different platforms and be more compatible."
"There is no local support team in Saudi Arabia."
"It could be more user-friendly and centralized. A way to reduce redundancy would be helpful."
"The pricing was high for our needs. We should not have to pay for features we do not use."
"It could use a tool to diagnose what is missing from the environment for WhereScape to install successfully."
"Technical support isn't the best."
"The ability to execute SSIS projects within WhereScape would be nice because we have a lot of packages that are too cumbersome to recreate."
"The scheduled jobs which are run by the WhereScape scheduler seem to be a strangely separate animal."
"Jobs cannot be deleted via the deployment package. When deploying from dev to QA or production, a job has to be retired."
"The solution can be a little more user-friendly on enterprise-level where people use it."
"I don't think the solution is very stable. Even though I like this tool numerous bugs made it difficult and unreliable."
"Data discovery would be more powerful with machine learning features."
 

Pricing and Cost Advice

"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"The solution is cheaper than other products."
"It comes with a high cost."
"Confluent is highly priced."
"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 has a yearly license, which is a bit high because it's on a per-user basis."
"You have to pay additional for one or two features."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"Factor in the price of specialized consulting who know this product. They're hard to find and expensive."
"Our company purchased a corporate unlimited license."
"ROI is at least 10 times."
"Speed to market of a warehouse solution at a relatively inexpensive price point."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
893,164 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Retailer
10%
Computer Software Company
10%
Manufacturing Company
5%
Healthcare Company
10%
Insurance Company
9%
Financial Services Firm
9%
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 Business6
Midsize Enterprise4
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...
Ask a question
Earn 20 points
 

Comparisons

 

Overview

 

Sample Customers

ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
British American Tobacco, Cornell University, Allianz Benelux, Finnair, Solarwinds and many more.
Find out what your peers are saying about Confluent vs. WhereScape RED and other solutions. Updated: April 2026.
893,164 professionals have used our research since 2012.