AWS Database Migration Service vs StreamSets comparison

Amazon Web Services (AWS) and IBM are both solutions in the Cloud Data Integration category. Additionally, 93% of Amazon Web Services (AWS) users are willing to recommend the solution, compared to 100% of IBM users who would recommend it.

AWS Database Migration Service

Read 30 AWS Database Migration Service reviews

6,530 Views
5,421 Comparison Views

93% willing to recommend

StreamSets

Read 24 StreamSets reviews

3,109 Views
1,983 Comparison Views

100% willing to recommend

AWS Database Migration Service

StreamSets

Comparison Buyer's Guide

Download the report

Executive Summary

We performed a comparison between AWS Database Migration Service and StreamSets based on real PeerSpot user reviews.

Find out in this report how the two Cloud Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.

To learn more, read our detailed AWS Database Migration Service vs. StreamSets Report (Updated: October 2024).

Buyer's Guide

AWS Database Migration Service vs. StreamSets

October 2024

Download the complete report

Helped 816,562 peers since 2012

Categories and Ranking

AWS Database Migration Service

Average Rating

8.0

Reviews Sentiment

6.4

Number of Reviews

Ranking in other categories

Cloud Data Integration (2nd)

StreamSets

Average Rating

8.4

Reviews Sentiment

7.5

Number of Reviews

Ranking in other categories

Data Integration (9th)

Featured Reviews

StevenLai

Sr. Data Engineer at Amrock

Straightforward to set up with easy of capturing database changes and secure storage

Sometimes we encounter errors, and the error messages from DMS are very ambiguous and sometimes misleading. For example, if we connect to an incorrect instance with incorrect setups, it will not say the connection failed. Instead, it says the DMS task failed with an unclear error message like 'subtask AWS failed', which does not help. The connection should fail if we are connecting to the wrong instance, but the endpoint connection still succeeds.

Read full review

Reyansh Kumar

Technical Specialist at Accenture

We no longer need to hire highly skilled data engineers to create and monitor data pipelines

The things I like about StreamSets are its * overall user interface * efficiency * product features, which are all good. Also, 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. You just need to configure the data sources, the paths and their configurations, and you are ready to go. It is very efficient and very easy to use for ETL pipelines. It is a GUI-based interface in which you can easily create or design your own data pipelines with just a few clicks. As for moving data into modern analytics systems, we are using it with Microsoft Power BI, AWS, and some on-premises solutions, and it is very easy to get data from StreamSets into them. No hardcore coding or special technical expertise is required. It is also a no-code platform in which you can configure your data sources and data output for easy configuration of your data pipeline. This is a very important aspect because if a tool requires code development, we need to hire software developers to get the task done. By using StreamSets, it can be done with a few clicks.

Read full review

Quotes from Members

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

Pros

"The product's initial setup phase was very easy."

"The most valuable features of the AWS Database Migration Service are the ease of migration, beneficial storage system, security, and simple instance creation. Additionally, the cloud that is provided is more complete than other solutions."

"The most valuable feature of the solution is the one I use for report generation. The security risk is very low."

"If your infrastructure is already on Amazon, it simply makes the most sense to use a tool officially provided by them as an additional service, rather than having to rely on a third-party solution."

"One of the features, I find most valuable is its ability to apply rules and transformations to data during real-time integration. This includes changing schema names or table structures on AWS without delaying the data flow. Initially, full migrations can vary widely in time depending on the source system; for instance, a large Magento database might take up to six months, while smaller databases like IBM DB2 could migrate within hours. Once set up, AWS DMS ensures real-time synchronization using Change Data Capture (CDC), maintaining data integrity throughout the process."

"The most valuable feature of AWS Database Migration Service is it catches all the history changes, such as inset, observe, and delete. It tracks everything."

"As the solution is on the cloud, we don't have to worry about the maintenance of software."

"Support is helpful."

More AWS Database Migration Service pros

"One of the things I like is the data pipelines. They have a very good design. Implementing pipelines is very straightforward. It doesn't require any technical skill."

"The UI is user-friendly, it doesn't require any technical know-how and we can navigate to social media or use it more easily."

"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."

"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."

"It's very easy to integrate. It integrates with Snowflake, AWS, Google Cloud, and Azure. It's very helpful for DevOps, DataOps, and data engineering because it provides a comprehensive solution, and it's not complicated."

"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 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."

"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."

More StreamSets pros

Cons

"Support could be more expedient. Right now I am waiting on support for an extension."

"The performance of data migration could be smoother."

"This solution can offer more tweaks where the latency can be brought down to fifteen seconds."

"The initial setup can be difficult for beginners in AWS Database Migration Service. You will need the training to complete it."

"More endpoints need to be supported by AWS Database Migration Service. There's also a need for more control and transparency on the product, including better technical support."

"There is no connectivity to the source database or the target database."

"Whatever solution worked today can not be reused in the next migration."

"The names of the services need improvement since AWS doesn't indicate what the function of the product is presently. You need to read a lot to find the service that you want in the product."

More AWS Database Migration Service cons

"Sometimes, when we have large amounts of data that is very efficiently stored in Hadoop or Kafka, it is not very efficient to run it through StreamSets, due to the lack of efficiency or the resources that StreamSets is using."

"Visualization and monitoring need to be improved and refined."

"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 was painful. Also, pipeline failures were common, and data drifting wasn't addressed, which made things worse. Licensing was another issue we encountered."

"Sometimes, it is not clear at first how to set up nodes. A site with an explanation of how each node works would be very helpful."

"Using ETL pipelines is a bit complicated and requires some technical aid."

"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."

"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."

"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."

More StreamSets cons

Pricing and Cost Advice

"In terms of pricing, I'd rate it an eight out of ten, considering it's a well-priced solution."

"Pricing can be improved."

"Cost is the only factor that is challenging."

"Pricing for the solution is reasonable, but could still be reduced."

"The solution’s pricing is reasonable."

"I would rate the pricing a seven out of ten."

"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 product is pretty expensive"

More AWS Database Migration Service pricing and cost advice

"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."

"We are running the community version right now, which can be used free of charge."

"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."

"It has a CPU core-based licensing, which works for us and is quite good."

"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 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 overall cost for small and mid-size organizations needs to be better."

"StreamSets is an expensive solution."

More StreamSets pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.

See recommendations

816,562 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

21%

Computer Software Company

14%

Government

Manufacturing Company

Financial Services Firm

17%

Computer Software Company

13%

Manufacturing Company

Insurance Company

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...

See all answers

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. ...

See all answers

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...

See all answers

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...

See all answers

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 ...

See all answers

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...

See all answers

Comparisons

AWS Glue vs AWS Database Migration Service

Compared 47% of the time

Oracle GoldenGate vs AWS Database Migration Service

Compared 16% of the time

Qlik Replicate vs AWS Database Migration Service

Compared 11% of the time

Fivetran vs AWS Database Migration Service

Compared 7% of the time

JumpMind SymmetricDS vs AWS Database Migration Service

Compared 1% of the time

More AWS Database Migration Service Competitors

Informatica PowerCenter vs StreamSets

Compared 13% of the time

IBM InfoSphere DataStage vs StreamSets

Compared 11% of the time

Fivetran vs StreamSets

Compared 10% of the time

webMethods.io vs StreamSets

Compared 9% of the time

Azure Data Factory vs StreamSets

Compared 8% of the time

More StreamSets Competitors

Product Reports

Buyer's Guide

AWS Database Migration Service

November 2024

Download AWS Database Migration Service product report

Buyer's Guide

StreamSets

October 2024

Download StreamSets product report

Also Known As

AWS Data Migration Service

No data available

Learn More

Amazon Web Services (AWS)

Video not available

IBM

Overview

AWS Database Migration Service, also known as AWS DMS, is a cloud service that facilitates the migration of relational databases, NoSQL databases, data warehouses, and other types of data stores. The product can be used to migrate users' data into the AWS Cloud or between combinations of on-premises and cloud setups. The solution allows migration between a wide variety of sources and target endpoints; the only requirement is that one of the endpoints has to be an AWS service. AWS DMS cannot be used to migrate from an on-premises database to another on-premises database.

AWS Database Migration Service allows users to perform one-time migrations, as well as replications of ongoing changes to keep sources and targets in sync. Organizations can utilize the AWS Schema Conversion Tool to translate their database schema to a new platform and then use AWS DMS to migrate the data. The product offers cost efficiency as a part of the AWS Cloud, as well as speed to market, flexibility, and security.

The main use cases of AWS Database Migration Service include:

Migrating from legacy or on-premises databases to managed cloud services through a simplified migration process.
Reliable replication of backup files to minimize downtime and data loss.
Improvement of integration through building of data lakes and performing real-time processing on change data from users' data stores.

AWS Database Migration Service Components

AWS Database Migration Service consists of various components which function together to achieve users’ data migration. A migration on AWS DMS is structured in three levels: a replication instance, source and target endpoints, and a replication task. The components include the following actions:

Replication instance: AWS Database Migration Service provides users with a variety of replication instances, allowing them to select the optimal configuration for their use case. Depending on the instance class an organization selects, their replication instance provides a different amount of data storage.
Endpoint: AWS DMS uses an endpoint to access users' source or target data stores. The connection information is different and depends on the specific data store, but it usually consists of the following information: endpoint type, engine type, server name, port, encryption, and credentials. This information can easily be managed through the AWS DMS console.
Replication tasks: AWS Database Migration Service replication tasks can be used to move a set of data from the source endpoint to the target endpoint. The creation of a replication task is the last required step before starting a migration. Each replication task requires the following settings to be set: replication instance, source endpoint, target endpoint, and migration type options.
Ongoing replication or change data capture (CDC): AWS DMS also has the capacity to capture ongoing changes to the source that is stored while users migrate their data to a target.
Schema and code migration: The product requires assistance from tools such as MySQL Workbench, pgAdmin III, and Oracle SQL Developer to perform schema or code conversion, as it cannot do it on its own.

AWS Database Migration Service Benefits

AWS Database Migration Service offers its users a wide range of benefits. Among them are the following:

The solution ensures minimal downtime, as it continuously replicates the changes to the user’s source database during migration.
AWS DMS provides users with flexibility, as it supports many commonly used databases, including commercial and open-source ones.
The product is user friendly, as it offers an easy set of tasks in the AWS Management Console.
Users of Aurora, Redshift, DocumentDB, and DynamoDB can benefit from the free use of AWS DMS.
AWS Database Migration Service is very reliable because it is a self-healing service that automatically restarts in cases of interruptions.
The product supports both homogenous migrations and heterogenous migrations.
AWS DMS accelerates business growth, as it scales businesses at an affordable price.

Reviews from Real Users

Vishal S., an infrastructure lead at a computer software company, likes AWS Database Migration Service because it is easy to use and set up.

Vinod K., a data analyst at AIMLEAP, describes AWS DMS as an easy solution to save and extract data.

StreamSets is a data integration platform that enables organizations to efficiently move and process data across various systems. It offers a user-friendly interface for designing, deploying, and managing data pipelines, allowing users to easily connect to various data sources and destinations. StreamSets also provides real-time monitoring and alerting capabilities, ensuring that data is flowing smoothly and any issues are quickly addressed.

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

Buyer's Guide

AWS Database Migration Service vs. StreamSets

October 2024

Free Report: AWS Database Migration Service vs. StreamSets

Find out what your peers are saying about AWS Database Migration Service vs. StreamSets and other solutions. Updated: October 2024.

DOWNLOAD NOW

816,562 professionals have used our research since 2012.

See our AWS Database Migration Service vs. StreamSets report.

See our list of best Cloud Data Integration vendors.

We monitor all Cloud Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.