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

SAP Process Orchestration vs StreamSets 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

SAP Process Orchestration
Average Rating
8.2
Reviews Sentiment
7.2
Number of Reviews
33
Ranking in other categories
Business-to-Business Middleware (2nd)
StreamSets
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
Data Integration (16th)
 

Mindshare comparison

SAP Process Orchestration and StreamSets aren’t in the same category and serve different purposes. SAP Process Orchestration is designed for Business-to-Business Middleware and holds a mindshare of 8.0%, down 12.6% compared to last year.
StreamSets, on the other hand, focuses on Data Integration, holds 1.6% mindshare, up 1.4% since last year.
Business-to-Business Middleware
Data Integration
 

Featured Reviews

Laxman  Molugu - PeerSpot reviewer
Enhances operational efficiency with valuable prepackaged content and cost-effective pricing
For organizations that operate within an SAP ecosystem, SAP Process Orchestration is recommended due to its cost-effectiveness and the availability of valuable prepackaged content. It is important to consider the needs of your industry, as SAP Process Orchestration may not meet all requirements in consumer-oriented sectors. I'd rate the solution eight out of ten.
Karthik Rajamani - PeerSpot reviewer
Integrates with different enterprise systems and enables us to easily build data pipelines without knowing how to code
There are a few things that can be better. We create pipelines or jobs in StreamSets Control Hub. It is a great feature, but if there is a way to have a folder structure or organize the pipelines and jobs in Control Hub, it would be great. I submitted a ticket for this some time back. There are certain features that are only available at certain stages. For example, HTTP Client has some great features when it is used as a processor, but those features are not available in HTTP Client as a destination. There could be some improvements on the group side. Currently, if I want to know which users are a part of certain groups, it is not straightforward to see. You have to go to each and every user and check the groups he or she is a part of. They could improve it in that direction. Currently, we have to put in a manual effort. In case something goes wrong, we have to go to each and every user account to check whether he or she is a part of a certain group or not.

Quotes from Members

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

Pros

"The solution's technical support is good."
"SAP Process Orchestration is middleware where we are able to manage and interact with everything from a single location. One of the most beneficial areas is monitoring which is very easy because it is all in one place. There are many adapters added recently that can be used for new functionality. The solution is easy to operate and it is more mature than the cloud solution provided by SAP."
"It provides essential features such as continuous monitoring of all interfaces are crucial for our needs."
"Overall, I would rate SAP Process Orchestration a 10 out of 10."
"The main benefit is that the solution is low maintenance. Moreover, it's the license cost is very low because it's part of the package. The maintenance is standard maintenance. And the updates are regular. So there's a regular update and you can choose whether you want to do those updates or not."
"The solution is easy to use."
"The most valuable feature of SAP Process Orchestration is its flexibility in being able to build integrations with SAP systems and non-SAP systems."
"The most valuable features of SAP Process Orchestration are its system monitoring and alerts."
"The ability to have a good bifurcation rate and fewer mistakes is valuable."
"Also, the intuitive canvas for designing all the streams in the pipeline, along with the simplicity of the entire product are very big pluses for me. The software is very simple and straightforward. That is something that is needed right now."
"The entire user interface is very simple and the simplicity of creating pipelines is something that I like very much about it. The design experience is very smooth."
"The most valuable feature is the pipelines because they enable us to pull in and push out data from different sources and to manipulate and clean things up within them."
"I have used Data Collector, Transformer, and Control Hub products from StreamSets. What I really like about these products is that they're very user-friendly. People who are not from a technological or core development background find it easy to get started and build data pipelines and connect to the databases. They would be comfortable like any technical person within a couple of weeks."
"StreamSets’ data drift resilience has reduced the time it takes us to fix data drift breakages. For example, in our previous Hadoop scenario, when we were creating the Sqoop-based processes to move data from source to destinations, we were getting the job done. That took approximately an hour to an hour and a half when we did it with Hadoop. However, with the StreamSets, since it works on a data collector-based mechanism, it completes the same process in 15 minutes of time. Therefore, it has saved us around 45 minutes per data pipeline or table that we migrate. Thus, it reduced the data transfer, including the drift part, by 45 minutes."
"The Ease of configuration for pipes is amazing. It has a lot of connectors. Mainly, we can do everything with the data in the pipe. I really like the graphical interface too"
"The ETL capabilities are very useful for us. We extract and transform data from multiple data sources, into a single, consistent data store, and then we put it in our systems. We typically use it to connect our Apache Kafka with data lakes. That process is smooth and saves us a lot of time in our production systems."
 

Cons

"I think the big improvement required in the tool stems from the fact that the whole issue around it is that we have some downtime failures during upgrades and patching."
"I feel that support is an area that needs improvement. They need to improve the response time and address the customer's issues as soon as possible."
"SAP Process Orchestration breaks down sometimes."
"The solution could be more scalable."
"The older version of the solution will no longer be supported."
"Some configurations can be a little tricky."
"It requires some maintenance."
"The cloud capability features need improvement."
"StreamSet works great for batch processing but we are looking for something that is more real-time. We need latency in numbers below milliseconds."
"The execution engine could be improved. When I was at their session, they were using some obscure platform to run. There is a controller, which controls what happens on that, but you should be able to easily do this at any of the cloud services, such as Google Cloud. You shouldn't have any issues in terms of how to run it with their online development platform or design platform, basically their execution engine. There are issues with that."
"We've seen a couple of cases where it appears to have a memory leak or a similar problem."
"Currently, we can only use the query to read data from SAP HANA. What we would like to see, as soon as possible, is the ability to read from multiple tables from SAP HANA. That would be a really good thing that we could use immediately. For example, if you have 100 tables in SQL Server or Oracle, then you could just point it to the schema or the 100 tables and ingestion information. However, you can't do that in SAP HANA since StreamSets currently is lacking in this. They do not have a multi-table feature for SAP HANA. Therefore, a multi-table origin for SAP HANA would be helpful."
"The monitoring visualization is not that user-friendly. It should include other features to visualize things, like how many records were streamed from a source to a destination on a particular date."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"There aren't enough hands-on labs, and debugging is also an issue because it takes a lot of time. Logs are not that clear when you are debugging, and you can only select a single source for a pipeline."
"One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infrastructure."
 

Pricing and Cost Advice

"My company deals with different pricing models of the product, according to which we don't pay for the solution directly, but we do pay for the maintenance part."
"Normally, you will have to choose CPU-based licensing...I rate the tool price a five out of ten."
"The solution is highly-priced."
"The price of SAP Process Orchestration was reasonable."
"The pricing for this solution is fine."
"It's not an expensive solution."
"The license is a one-time payment, and additional costs are only incurred on the infrastructure side since it's an on-premise solution."
"The product is not a low-priced solution, but I can say that it is competitively priced in the market."
"There are different versions of the product. One is the corporate license version, and the other one is the open-source or free version. I have been using the corporate license version, but they have recently launched a new open-source version so that anybody can create an account and use it. The licensing cost varies from customer to customer. I don't have a lot of input on that. It is taken care of by PMO, and they seem fine with its pricing model. It is being used enterprise-wide. They seem to have got a good deal for StreamSets."
"StreamSets Data Collector is open source. One can utilize the StreamSets Data Collector, but the Control Hub is the main repository where all the jobs are present. Everything happens in Control Hub."
"Its pricing is pretty much up to the mark. For smaller enterprises, it could be a big price to pay at the initial stage of operations, but the moment you have the Seed B or Seed C funding and you want to scale up your operations and aren't much worried about the funds, at that point in time, you would need a solution that could be scaled."
"The licensing is expensive, and there are other costs involved too. I know from using the software that you have to buy new features whenever there are new updates, which I don't really like. But initially, it was very good."
"The pricing is affordable for any business."
"The pricing is too fixed. It should be based on how much data you need to process. Some businesses are not so big that they process a lot of data."
"It's not so favorable for small companies."
"The overall cost is very flexible so it is not a burden for our organization... However, the cost should be improved. For small and mid-size organizations it might be a challenge."
report
Use our free recommendation engine to learn which Business-to-Business Middleware solutions are best for your needs.
850,236 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
17%
Computer Software Company
15%
Financial Services Firm
8%
Energy/Utilities Company
6%
Financial Services Firm
13%
Computer Software Company
11%
Manufacturing Company
10%
Insurance Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about SAP Process Orchestration?
It provides essential features such as continuous monitoring of all interfaces are crucial for our needs.
What is your experience regarding pricing and costs for SAP Process Orchestration?
The main concern is the cost. If additional help is needed due to lack of skill, we have to pay for SAP support.
What needs improvement with SAP Process Orchestration?
There are two main areas for improvement: performance and cost. The cost is quite high, and if it were reduced, it might also improve the performance, potentially allowing us to access a more effic...
What do you like most about StreamSets?
The best thing about StreamSets is its plugins, which are very useful and work well with almost every data source. It's also easy to use, especially if you're comfortable with SQL. You can customiz...
What needs improvement with StreamSets?
One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infr...
What is your primary use case for StreamSets?
We are using StreamSets for batch loading.
 

Also Known As

SAP NetWeaver Process Integration, NetWeaver Process Integration
No data available
 

Overview

 

Sample Customers

Lenovo, Dansk Supermarked A/S, Ego Pharmaceuticals Pty. Ltd, Kaeser Kompressoren
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about SAP Process Orchestration vs. StreamSets and other solutions. Updated: April 2025.
850,236 professionals have used our research since 2012.