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

AWS AppSync 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

AWS AppSync
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
2
Ranking in other categories
Cloud Data Integration (23rd)
StreamSets
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
Data Integration (22nd)
 

Featured Reviews

Akil Saji - PeerSpot reviewer
Ease of creating APIs with ongoing updates needed for automation
AWS has made it easy for developers like me to create and manage GraphQL APIs. The ease of use is a main advantage, allowing even beginners to start from scratch and learn through AppSync. Before AWS, developing and managing APIs was quite complex. AWS provided AppSync, which assists developers and startup founders. Startups blooming everywhere benefit from this service, welcoming those who lack prior knowledge. When working on AWS, I notice that Amazon regularly implements new features. For instance, with the Lambda service, AWS is transitioning from an old editor to a new one. Similarly, AppSync frequently introduces updates and changes. This trend is making the user interface more accessible, even for individuals without a technical background. Additionally, the cost is attractive, as AWS operates on a pay-as-you-go basis. These factors make AppSync both easy to use and cost-effective.
Ved Prakash Yadav - PeerSpot reviewer
Useful for data transformation and helps with column encryption
We use various tools and alerting systems to notify us of pipeline errors or failures. StreamSets supports data governance and compliance by allowing us to encrypt incoming data based on specified rules. We can easily encrypt columns by providing the column name and hash key. If you're considering using StreamSets for the first time, I would advise first understanding why you want to use it and how it will benefit you. If you're dealing with change tracking or handling large amounts of data, it could be cost-effective compared to services like Amazon. It's easy to schedule and manage tasks with the tool, and you can enhance your skills as an ETL developer. You can easily migrate traditional pipelines built on platforms like Informatica or Talend to StreamSets. I rate the overall solution an eight out of ten.

Quotes from Members

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

Pros

"AWS has made it easy for developers like me to create and manage GraphQL APIs."
"Support for multiple data sources and formats is a fantastic feature."
"AWS has made it easy for developers like me to create and manage GraphQL APIs."
"What I love the most is that StreamSets is very light. It's a containerized application. It's easy to use with Docker. If you are a large organization, it's very easy to use Kubernetes."
"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."
"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."
"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."
"For me, the most valuable features in StreamSets have to be the Data Collector and Control Hub, but especially the Data Collector. That feature is very elegant and seamlessly works with numerous source systems."
"In StreamSets, everything is in one place."
"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 most valuable features are the option of integration with a variety of protocols, languages, and origins."
 

Cons

"In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial."
"Moving to other clouds is impossible without significantly rearchitecting your applications."
"In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"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."
"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."
"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."
"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."
"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."
"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 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."
 

Pricing and Cost Advice

"Licensing fees are paid on a monthly basis, and it is a pay-as-you-go model."
"The pricing is affordable for any business."
"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."
"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."
"We are running the community version right now, which can be used free of charge."
"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."
"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."
"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."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
856,874 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Computer Software Company
18%
Healthcare Company
10%
Real Estate/Law Firm
8%
Financial Services Firm
13%
Computer Software Company
11%
Manufacturing Company
10%
Insurance Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for AWS AppSync?
We initially had limited knowledge about AWS costs. As beginners, we ran many instances for over a month. Consequently, we received a bill from Amazon for around $20, which was unexpected. This hig...
What needs improvement with AWS AppSync?
In AppSync, assigning roles and permissions to APIs is necessary for accessing other AWS services. Automating this task when creating APIs would be beneficial. Regular updates might soon address th...
What is your primary use case for AWS AppSync?
Our company handles in-house projects and serves clients globally. My role with AppSync involves creating GraphQL APIs. There are different types of APIs, such as REST API, GraphQL API, and WebSock...
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.
 

Comparisons

 

Also Known As

AppSync
No data available
 

Overview

 

Sample Customers

ACBL, Puresec, IDT, ASU, Public Good, cookpad, ALDO, ticketmaster
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about AWS AppSync vs. StreamSets and other solutions. Updated: June 2025.
856,874 professionals have used our research since 2012.