AWS Database Migration Service Reviews

I have used it for anything analytical, assisting in making the data available as quickly as possible from upstream systems to the downstream system.

We have the ability to bring data for all tables of a database in one go, as long as the tables follow a particular naming convention. I can use wild characters to bring all of those tables in one go rather than maintaining a series of table names. 

Additionally, I am using AWS for our daily lifecycle, providing ease of doing things. AWS offers a way to build jobs that are scalable, expandable for new and current tables, and can be deployed quickly. This efficient workflow has been particularly helpful.

I work for a company that was in the process of migrating a couple hundred servers to the cloud from on-premises. This is where we used the AWS Database Migration Service.

One valuable feature of AWS Database Migration Service is change data capture (CDC). You can copy the database at first without impacting your current database, and then use CDC to copy incremental changes. The switchover is also very convenient when you switch over from the current database to the new one. This helps save time because you do not need to buy servers, and AWS recommends target server configurations. This eliminates the typical low-level technical work like setting up the server and networking, which helps significantly.

We are setting up CDT jobs to get database changes from AWS RDS. We are not really migrating anything, but we get the changes from our source RDS instance and save it as a file in an S3 bucket.

For our continuity planning, we need all the history happening in the source database because AWS source database does not store history there. By capturing all the changes from our AWS instance and storing it in an S3 bucket, we can do whatever transformation we want without the fear of losing data. The confidence it gives us is ensuring we have the data. As long as we don’t delete these data, we always have this historical database.

We use AWS Database Migration Service to integrate data using Change Data Capture (CDC) functionality. Instead of directly accessing the database, we monitor the database log files for any data changes, adhering to the CDC concept. This approach ensures real-time data synchronization without impacting the production database or data files themselves. It allows us to maintain a live, up-to-date integration with AWS and update dashboards accordingly.

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.

We used the solution for live replication but faced many access challenges. We moved to make a full copy and then use column-level filtering to achieve incremental load. Over time, we get the necessary access permissions, allowing us to switch to live replication. We experienced a delay of roughly two minutes, which was not an issue for our use case.

When AWS Database Migration Service started working correctly, we had approximately 300 tables replicating from Oracle and other databases into AWS S3. Subsequently, any changes, such as full replication or percentage increments, could be easily accomplished by executing additional DMS tasks. DMS was configurable and straightforward to use. They were also scaling the scheduling of DMS drops. There are so many different options available.

We use an airflow instance on AWS to scale and schedule DMS tasks. This has allowed us to retire nearly 350 Informatica or injection jobs and consolidate them into DMS, a cost-effective service.

DMS's architecture is highly beneficial, allowing for scalable migrations of large datasets. The service's change data capture feature is precious, enabling synchronization between the old and new systems, and providing customers with real-time data visibility.

There could be enhancements in the product intelligently covering more scenarios to prevent crashes or failures. Improved dashboard capabilities for monitoring jobs and the ability to resume migrations from the last successful point instead of starting over would significantly enhance the user experience.

Currently, in our company, we use the product as a part of our strategy since we recently got involved in the area of migration.

I use AWS Database Migration Service in my company for whatever applications are developed on an on-premises infrastructure since such applications have fewer scalability features when compared to the cloud. Suppose you move the applications to the cloud. In that case, the scalability can be very high, and the number of users who are going to use the product can be controlled. AWS should develop an industry-competent product so that its users can compete with other technologies and companies.

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

My company uses AWS Database Migration Service as a small data warehouse.

What I like about AWS Database Migration Service is that it is available on the cloud, and you don't need any admins. If you want the backup then you can store it online directly. With the product in place, users can focus on what they want to do, and there is no need to do a lot of maintenance as there are no complications that arise in the tool. It is a maintenance-free product.