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

AWS Database Migration Service 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 Database Migration Service
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
31
Ranking in other categories
Cloud Data Integration (2nd)
StreamSets
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
Data Integration (15th)
 

Featured Reviews

Avinash Gangu - PeerSpot reviewer
Centralizing database tables enhances workflow efficiency for ease of use
I was looking for some content as part of a comparison analysis. However, one of the pain points is that it is way too free-flowing. I have to skim through all the security pages to get to the crux of it. I was looking for a table that suggests which facets such services address with proofs of reference from professional conferences. The document is a 63-page read, making it very difficult to navigate without a summary. I was looking for a summary at the start, however, if I have to do it myself, I might as well integrate from AWS Docs and then Informative Exchange. The current document contains a lot of information, which is great, but there needs to be a summary indicating the story's essence. Unless there's a correction, it is not present in the document.
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 the solution is the one I use for report generation. The security risk is very low."
"One valuable feature of AWS Database Migration Service is change data capture (CDC)."
"As the solution is on the cloud, we don't have to worry about the maintenance of software."
"The initial setup is simple. Not that much complex."
"The product's initial setup phase was very easy."
"The solution is instantaneous. We can launch the service and reduce the end number of manpower."
"The process is now simplified because there won't be maintenance. Usually we can take a snapshot of the number I need. We can automate the backup snapshots and we can restore it very quickly. We get many benefits from the application."
"The solution is stable and reliable."
"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."
"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."
"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 customize it to do what you need. Many other tools have started to use features similar to those introduced by StreamSets, like automated workflows that are easy to set up."
"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."
"The most valuable would be the GUI platform that I saw. I first saw it at a special session that StreamSets provided towards the end of the summer. I saw the way you set it up and how you have different processes going on with your data. The design experience seemed to be pretty straightforward to me in terms of how you drag and drop these nodes and connect them with arrows."
"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 scheduling within the data engineering pipeline is very much appreciated, and it has a wide range of connectors for connecting to any data sources like SQL Server, AWS, Azure, etc. We have used it with Kafka, Hadoop, and Azure Data Factory Datasets. Connecting to these systems with StreamSets is very easy."
 

Cons

"The initial setup can be difficult for beginners in AWS Database Migration Service. You will need the training to complete it."
"One area that AWS DMS can improve on is its conversion of data types. For example, in Oracle, you have a data type called RAW, but in PostgreSQL there is no such thing. Thus, AWS DMS doesn't know what type I want to use when migrating from Oracle to PostgreSQL, and when performing the migration, AWS DMS changed the RAW data type to the byte data type, which isn't what I wanted."
"Support could be more expedient. Right now I am waiting on support for an extension."
"When working with AWS GovCloud, we often did not get an answer in time because AWS seemed more focused on the commercial side."
"The live duplication has a delay of two minutes, which can be an issue."
"The performance of data migration could be smoother."
"In my experience, AWS Database Migration Service performs well for its primary purpose of data migration. One area that could be improved is its support for non-AWS file formats, particularly when integrating data from sources stored outside of AWS. For example, handling AWS Data Lakes, Delta Lake, or Hadoop file formats stored in S3 requires extensive configuration and isn't always straightforward. It would be beneficial to streamline this process to ensure smoother migrations from non-AWS environments to AWS. As for additional functionality, I think enhancing support for these external file formats and simplifying configuration steps would be valuable improvements for the service."
"Whatever solution worked today can not be reused in the next migration."
"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."
"In terms of the product, I don't think there is any room for improvement because it is very good. One small area of improvement that is very much needed is on the knowledge base side. Sometimes, it is not very clear how to set up a certain process or a certain node for a person who's using the platform for the first time."
"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."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"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."
"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."
"One area for improvement could be the cloud storage server speed, as we have faced some latency issues here and there."
 

Pricing and Cost Advice

"Pricing for the solution is reasonable, but could still be reduced."
"Pricing can be improved."
"In terms of pricing, I'd rate it an eight out of ten, considering it's a well-priced solution."
"AWS Database Migration Service is the least expensive solution, but is still expensive."
"I rate the product price a seven on a scale of one to ten, where one is a high price, and ten is a low price."
"The solution’s pricing is reasonable."
"AWS Database Migration Service is very inexpensive."
"For Egypt, the product's prices are high, making it a specific problem in one region and not globally."
"There are two editions, Professional and Enterprise, and there is a free trial. We're using the Professional edition and it is competitively priced."
"I believe the pricing is not equitable."
"It's not so favorable for small companies."
"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."
"It has a CPU core-based licensing, which works for us and is quite good."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
848,989 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
15%
Government
7%
Manufacturing Company
7%
Financial Services Firm
14%
Computer Software Company
11%
Manufacturing Company
9%
Insurance Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What resources can you use to learn how to utilize AWS Database Migration Service?
As with all AWS products, you are given very useful documentation with AWS Database Migration Service. Before we started using this product, we went over it and we were able to learn the basics an...
Would you recommend AWS Database Migration Service as a cloud data integration tool?
My current company started using AWS Database Migration Service upon my recommendation, and I continue telling people how good of a product it is. However, users should keep in mind a few things. ...
Is AWS Database Migration Service an affordable solution?
Compared to similar solutions, AWS Database Migration Service falls somewhere in the middle price-wise, at least from my experience. This being said, it is not a very affordable solution, especial...
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

AWS Data Migration Service
No data available
 

Overview

 

Sample Customers

Veoci, Trimble, Nasdaq, shaadi.com, Hotelbeds, SysAid, Verizon, Expedia, Pega
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about AWS Database Migration Service vs. StreamSets and other solutions. Updated: April 2025.
848,989 professionals have used our research since 2012.