Database Migration on Premises to AWS RDS

For the past four decades, the traditional relational databases have been in use in Information Technology industry. There was a phenomenal conversion in the IT industry in terms of commercial applications in the previous years. The applications that were running on a Single server in organizations IT infrastructure have been replaced or migrated with e-apps. Also, the dedicated storages are replaced with system storages. The model of pay per use, flexibility and lesser cost are the main reasons, which caused the distributed computing pick up into reality. Cloud databases, Simple DB, and Amazon RDS are getting to be more familiar to communities because they have brought up and highlighted the issues and problems of current social databases in terms of usability, flexibility, and provisioning. Basically now, the cloud databases are at present considered as a solution for programmers, designers, and architects since they need to store the information of their applications in an adaptable and exceptionally accessible from backend when required. These Database-as-a-Service (DBaaS) administrations are cloud-based information stockpiling administrations can be arranged into two principle classifications: benefits that backing conventional social databases (RDB) (e.g., Amazon RDS, Google SQL, Microsoft Azure), and key/quality pair information stockpiling administrations (e.g., Amazon Simple DB, Google Data Store), which are otherwise called NoSQL Databases [Harrison John Bhatti and Babak Bashari Rad 2017]. In this paper, we are going to analyze and perform one such On-Premises to AWS RDS To support, Cloud migration which helps the users on performance, cost, and scalability