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
32
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 (15th)
 

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.6%, down 13.0% compared to last year.
StreamSets, on the other hand, focuses on Data Integration, holds 1.6% mindshare, up 1.3% 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 most valuable feature of SAP Process Orchestration is its flexibility in being able to build integrations with SAP systems and non-SAP systems."
"The solution is easy to use."
"I think it is a very stable tool. My company did not have any problem with the tool."
"The initial setup was straightforward."
"It is a scalable solution."
"SAP Process Orchestration provides extensive integrations with external partners, supports B2B operations, and has prepackaged content that saves development time."
"t is a pretty stable solution. I have not seen any outages in the solution."
"The product has good technical support but you usually will not need it because it is quite stable."
"StreamSets Transformer is a good feature because it helps you when you are developing applications and when you don't want to write a lot of code. That is the best feature overall."
"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."
"I really appreciate the numerous ready connectors available on both the source and target sides, the support for various media file formats, and the ease of configuring and managing pipelines centrally."
"It is really easy to set up and the interface is easy to use."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"The ability to have a good bifurcation rate and fewer mistakes is valuable."
"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."
"StreamSets data drift feature gives us an alert upfront so we know that the data can be ingested. Whatever the schema or data type changes, it lands automatically into the data lake without any intervention from us, but then that information is crucial to fix for downstream pipelines, which process the data into models, like Tableau and Power BI models. This is actually very useful for us. We are already seeing benefits. Our pipelines used to break when there were data drift changes, then we needed to spend about a week fixing it. Right now, we are saving one to two weeks. Though, it depends on the complexity of the pipeline, we are definitely seeing a lot of time being saved."
 

Cons

"Its administration management feature needs to be simpler to use."
"Process Orchestration needs to provide secure connectivity as no one has any data information."
"In terms of technical support, it would be helpful if they handled the tickets a bit faster when queries are sent to them."
"SAP Process Orchestration breaks down sometimes."
"It is not a scalable solution for the cloud. I would not recommend this for the cloud."
"SAP should improve the user interface, as it often lacks modern features and aesthetic appeal."
"It is scalable, but there can be performance issues with high data volume or traffic, especially during month ends."
"Process Orchestration doesn't provide authentication for data sent to us, meaning we have to rely on client certificate-based or basic authentication."
"They need to improve their customer care services. Sometimes it has taken more than 48 hours to resolve an issue. That should be reduced. They are aware of small or generic issues, but not the more technical or deep issues. For those, they require some time, generally 48 to 72 hours to respond. That should be improved."
"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 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."
"The design experience is the bane of our existence because their documentation is not the best. Even when they update their software, they don't publish the best information on how to update and change your pipeline configuration to make it conform to current best practices. We don't pay for the added support. We use the "freeware version." The user community, as well as the documentation they provide for the standard user, are difficult, at best."
"One thing that I would like to add is the ability to manually enter data. The way the solution currently works is we don't have the option to manually change the data at any point in time. Being able to do that will allow us to do everything that we want to do with our data. Sometimes, we need to manually manipulate the data to make it more accurate in case our prior bifurcation filters are not good. If we have the option to manually enter the data or make the exact iterations on the data set, that would be a good thing."
"The logging mechanism could be improved. If I am working on a pipeline, then create a job out of it and it is running, it will generate constant logs. So, the logging mechanism could be simplified. Now, it is a bit difficult to understand and filter the logs. It takes some time."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"StreamSets should provide a mechanism to be able to perform data quality assessment when the data is being moved from one source to the target."
 

Pricing and Cost Advice

"The fee for maintenance is costly."
"There are fees in addition to the licensing."
"The price of SAP Process Orchestration was reasonable."
"The product is not a low-priced solution, but I can say that it is competitively priced in the market."
"It's not an expensive solution."
"The cost of SAP products is quite high but the quality is really good."
"We subscribe to annual licenses, and the competitive license cost is reasonable."
"The pricing for this solution is fine."
"We use the free version. It's great for a public, free release. Our stance is that the paid support model is too expensive to get into. They should honestly reevaluate that."
"We are running the community version right now, which can be used free of charge."
"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."
"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."
"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."
"It's not so favorable for small companies."
"The pricing is affordable for any business."
report
Use our free recommendation engine to learn which Business-to-Business Middleware solutions are best for your needs.
847,862 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
18%
Computer Software Company
15%
Financial Services Firm
7%
Energy/Utilities Company
5%
Financial Services Firm
14%
Computer Software Company
11%
Manufacturing Company
9%
Insurance Company
8%
 

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?
We often faced problems, especially with SAP ERP. We struggled because many columns weren't integers or primary keys, which StreamSets couldn't handle. We had to restructure our data tables, which ...
What is your primary use case for StreamSets?
StreamSets is used for data transformation rather than ETL processes. It focuses on transforming data directly from sources without handling the extraction part of the process. The transformed data...
 

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.
847,862 professionals have used our research since 2012.