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

Confluent vs SAS Data Integration Server 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 (3rd)
SAS Data Integration Server
Average Rating
7.2
Reviews Sentiment
6.5
Number of Reviews
4
Ranking in other categories
Data Integration (41st)
 

Mindshare comparison

Confluent and SAS Data Integration Server aren’t in the same category and serve different purposes. Confluent is designed for Streaming Analytics and holds a mindshare of 8.5%, down 9.7% compared to last year.
SAS Data Integration Server, on the other hand, focuses on Data Integration, holds 0.6% mindshare, up 0.5% since last year.
Streaming Analytics Market Share Distribution
ProductMarket Share (%)
Confluent8.5%
Apache Flink14.8%
Databricks12.5%
Other64.2%
Streaming Analytics
Data Integration Market Share Distribution
ProductMarket Share (%)
SAS Data Integration Server0.6%
Informatica PowerCenter6.0%
SSIS5.7%
Other87.7%
Data Integration
 

Featured Reviews

PavanManepalli - PeerSpot reviewer
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.
NN
Offloads processes on the server side but needs better installation syntax
One area for improvement is the installation process. Another point could be the syntax, as it sometimes involves using syntax names that are not intuitive. For example, to calculate the difference between two dates, the general syntax in SAS is called the data difference or data net function. However, another name is used, such as NF and INK. Without knowledge of SAS programming, it becomes unclear what these functions mean. It is not good to define function names this way.

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 solution can handle a high volume of data because it works and scales well."
"The biggest benefit of Confluent as a tool is that it is a distributed platform that provides more durability and stability."
"The documentation process is fast with the tool."
"It is also good for knowledge base management."
"Confluent facilitates the messaging tasks with Kafka, streamlining our processes effectively."
"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 features I find most useful in Confluent are the Multi-Region Cluster, MRC, and the Cluster Linking for replication."
"A key feature allows us to enhance job performance by offloading processing to the server side, rather than processing on the server itself."
"A key feature allows us to enhance job performance by offloading processing to the server side, rather than processing on the server itself."
"The most valuable feature of the solution is its amazing capabilities in regard to data handling."
"The solution offers very good data manipulation and loading."
"A key feature allows us to enhance job performance by offloading processing to the server side, rather than processing on the server itself."
"The solution is very stable."
 

Cons

"It could be improved by including a feature that automatically creates a new topic and puts failed messages."
"Areas for improvement include implementing multi-storage support to differentiate between database stores based on data age and optimizing storage costs."
"The pricing model should include the ability to pick features and be charged for them only."
"The Schema Registry service could be improved. I would like a bigger knowledge base of other use cases and more technical forums. It would be good to have more flexible monitoring features added to the next release as well."
"Confluent has fallen behind in being the tool of the industry. It's taking second place to things such as Word and SharePoint and other office tools that are more dynamic and flexible than Confluent."
"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."
"The formatting aspect within the page can be improved and more powerful."
"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 initial setup had issues, and even after using it for about one year, it was still not fixed."
"So I would like to see improved integration with other software."
"The initial setup had issues, and even after using it for about one year, it was still not fixed."
"One area for improvement is the installation process."
"The transform tool has limited access. They should make it more flexible."
"The initial setup of SAS Data Integration Server was complex."
 

Pricing and Cost Advice

"The solution is cheaper than other products."
"Confluent has a yearly license, which is a bit high because it's on a per-user basis."
"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."
"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."
"Confluent is an expensive solution."
"Confluent is expensive, I would prefer, Apache Kafka over Confluent because of the high cost of maintenance."
"Confluent is an expensive solution as we went for a three contract and it was very costly for us."
"It is an expensive program."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
869,760 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Computer Software Company
13%
Retailer
7%
Manufacturing Company
6%
Financial Services Firm
28%
Computer Software Company
8%
Insurance Company
7%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise4
Large Enterprise16
No data available
 

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?
People do not appreciate that Confluent is pushing us more towards Teams because they want to use a true Microsoft Word-type format where we can format our sentences better, instead of just saying ...
What needs improvement with SAS Data Integration Server?
One area for improvement is the installation process. Another point could be the syntax, as it sometimes involves using syntax names that are not intuitive. For example, to calculate the difference...
What is your primary use case for SAS Data Integration Server?
I am involved in the ETR job. My role is focused on executing the ETR job.
What advice do you have for others considering SAS Data Integration Server?
I use it without further details. For example, if I use SAS to connect to a NetEazt database or purchase a shared asset to ODBC, I can connect to any database with ODBC connection support. The over...
 

Also Known As

No data available
SAS Enterprise Data Integration Server, Enterprise Data Integration Server
 

Overview

 

Sample Customers

ING, Priceline.com, Nordea, Target, RBC, Tivo, Capital One, Chartboost
Credit Guarantee Corporation, Cr_dito y Cauci‹n, Delaware State Police, Deutsche Lufthansa, Directorate of Economics and Statistics, DSM, Livzon Pharmaceutical Group, Los Angeles County, Miami Herald Media Company, Netherlands Enterprise Agency, New Zealand Ministry of Health, Nippon Paper, West Midlands Police, XS Inc., Zenith Insurance
Find out what your peers are saying about Confluent vs. SAS Data Integration Server and other solutions. Updated: September 2025.
869,760 professionals have used our research since 2012.