MSP Bank, Limited is a leading Japanese monetary institution that provides a full range of financial products and services to both institutional and individual customers.
It is headquartered in Tokyo.
MSP Bank is hosting their existing infrastructure on premise. MSP bank has lot of web applications, databases and data warehouse built on Teradata, NoSQL databases, and other types of data stores.
MSP bank has lot of data assets in terms of logs, documents; excel files, CSV files, PDF documents and others. MSP Bank is running one of their web application NODE.JS supported by MSSQL relational database.
The schema designed is based on 3NF.
The Web Application has different user workloads at different parts of the day. MSP Bank is looking to keep the migration simple.
As a part of the migration, MSP bank needs some inputs on migration on the following Migration of MySQL database to a managed relational database with performance of up to 5 times the existing implementation Database to support both read and write workloads, with READ queries do not impact write query performance select 2 options.
Click on the arrows to vote for the correct answer
A. B. C. D. E. F.Answer: A, E.
Option A is correct - Migration of MySQL on premise to Aurora database.
Amazon Aurora (Aurora) is a fully managed relational database engine that's compatible with MySQL and PostgreSQL.
Aurora can deliver up to five times the throughput of MySQL.
An Amazon Aurora DB cluster consists of one or more DB instances and a cluster volume that manages the data for those DB instances.
An Aurora cluster volume is a virtual database storage volume that spans multiple Availability Zones, with each Availability Zone having a copy of the DB cluster data.
Two types of DB instances make up an Aurora DB cluster:
Primary DB instance - Supports read and write operations, and performs all of the data modifications to the cluster volume.
Each Aurora DB cluster has one primary DB instance.
Aurora Replica - Connects to the same storage volume as the primary DB instance and supports only read operations.
Each Aurora DB cluster can have up to 15 Aurora Replicas in addition to the primary DB instance.
Maintain high availability by locating Aurora Replicas in separate Availability Zones.
Aurora automatically fails over to an Aurora Replica in case the primary DB instance becomes unavailable.
You can specify the failover priority for Aurora Replicas.
Aurora Replicas can also offload read workloads from the primary DB instance.
Since Migration from MySQL to MySQL is a straight forward migration, migration will be simple.
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.htmlOption B is incorrect -Migration of MySQL to PostgreSQL is not encouraged because the migration of data between different databases makes migration complex and does not guarantee 5 times performance in terms of implementation.
An Amazon Aurora DB cluster consists of one or more DB instances and a cluster volume that manages the data for those DB instances.
An Aurora cluster volume is a virtual database storage volume that spans multiple Availability Zones, with each Availability Zone having a copy of the DB cluster data.
Two types of DB instances make up an Aurora DB cluster:
Primary DB instance - Supports read and write operations, and performs all of the data modifications to the cluster volume.
Each Aurora DB cluster has one primary DB instance.
Aurora Replica - Connects to the same storage volume as the primary DB instance and supports only read operations.
Each Aurora DB cluster can have up to 15 Aurora Replicas in addition to the primary DB instance.
Maintain high availability by locating Aurora Replicas in separate Availability Zones.
Aurora automatically fails over to an Aurora Replica in case the primary DB instance becomes unavailable.
You can specify the failover priority for Aurora Replicas.
Aurora Replicas can also offload read workloads from the primary DB instance.
Since Migration from MySQL to MySQL is a straight forward migration, migration will be simple.
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.htmlOption C is incorrect -Migration of MySQL to RDS is not a right option since it does not guarantee 5 times performance improvement compared to standard implementation.
Amazon Relational Database Service (Amazon RDS) is a web service that makes it easier to set up, operate, and scale a relational database in the cloud.
It provides cost-efficient, resizable capacity for an industry- standard relational database and manages common database administration tasks.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Welcome.htmlOption D is incorrect -Migration of MySQL to cluster built on EC2 instances is not a managed service.
This makes the setup and migration very complex.
Instead the team can go ahead with Aurora which provides 5 times performance compared to standard implementation, a managed service and also segregates read and write workloads through replica servers.
An Amazon Aurora DB cluster consists of one or more DB instances and a cluster volume that manages the data for those DB instances.
An Aurora cluster volume is a virtual database storage volume that spans multiple Availability Zones, with each Availability Zone having a copy of the DB cluster data.
Two types of DB instances make up an Aurora DB cluster:
Primary DB instance - Supports read and write operations, and performs all of the data modifications to the cluster volume.
Each Aurora DB cluster has one primary DB instance.
Aurora Replica - Connects to the same storage volume as the primary DB instance and supports only read operations.
Each Aurora DB cluster can have up to 15 Aurora Replicas in addition to the primary DB instance.
Maintain high availability by locating Aurora Replicas in separate Availability Zones.
Aurora automatically fails over to an Aurora Replica in case the primary DB instance becomes unavailable.
You can specify the failover priority for Aurora Replicas.
Aurora Replicas can also offload read workloads from the primary DB instance.
https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.htmlOption E is correct -Since Migration of data from MySQL to Aurora MySQL is a standard Migration, DMS would fulfill the requirement.
There is no schema conversion involved in the implementation
https://docs.aws.amazon.com/dms/latest/userguide/Welcome.htmlOption F is incorrect - Since migration is between same databases, schema conversion is not needed.
Use the AWS Schema Conversion Tool (AWS SCT) to translate your database schema to the new platform.
Use AWS DMS to migrate the data convert relational OLTP schema, or data warehouse schema.
Your converted schema is suitable for an Amazon Relational Database Service (Amazon RDS) MySQL DB instance, an Amazon Aurora DB cluster, an Amazon RDS PostgreSQL DB instance, or an Amazon Redshift cluster
https://docs.aws.amazon.com/SchemaConversionTool/latest/userguide/CHAP_Welcome.htmlMSP Bank is looking to migrate their MySQL database to a managed relational database that can support both read and write workloads with the performance of up to 5 times their existing implementation. The migration should be simple and not impact the existing workload on the web application.
Option A - Migrate MySQL Server to Amazon Aurora database MYSQL version with Aurora supporting read replicas which enables segregation of read and write workloads to primary and read replicas and provides 5 times performance compared to standard MySQL: Amazon Aurora is a managed relational database service that is compatible with MySQL and PostgreSQL. Aurora provides five times the performance of standard MySQL and PostgreSQL databases. It supports read replicas which enable the segregation of read and write workloads to primary and read replicas. This option meets the requirements of MSP Bank.
Option B - Migrate MySQL Server to Amazon Aurora database PostgreSQL version, as PostgreSQL is more performant compared to MySQL and provides 5 times performance compared to standard MySQL: This option suggests migrating the MySQL database to an Aurora database that is compatible with PostgreSQL. While PostgreSQL is known to be more performant than MySQL, this option may require a change in the application code to adapt to the new database engine. Additionally, it is unclear how Aurora PostgreSQL would perform in comparison to Aurora MySQL in MSP Bank's specific use case.
Option C - Migrate MySQL Server to Amazon RDS database MYSQL version, with RDS supporting read replicas which enables segregation of read and write workloads to primary and read replicas and provides 5 times performance compared to standard MySQL: Amazon RDS is a managed relational database service that supports MySQL, PostgreSQL, Oracle, SQL Server, and MariaDB. It provides read replicas which enable the segregation of read and write workloads to primary and read replicas. However, it is unclear if Amazon RDS MySQL would provide a performance increase of up to 5 times MSP Bank's existing implementation.
Option D - Migrate MySQL Server to MySQL cluster built on EC2 machines, configure cluster to support read replicas which enables segregation of read and write workloads to primary and read replicas: This option involves setting up a MySQL cluster on Amazon EC2 instances and configuring it to support read replicas. However, this option is not a managed service and would require MSP Bank to manage the cluster themselves. It may also require more effort to configure and maintain compared to the other options.
Option E - Use Data Migration Service (DMS) to address migration of MySQL database on premise to database on AWS cloud: AWS Data Migration Service (DMS) is a managed service that simplifies and accelerates database migration to AWS. It supports MySQL, PostgreSQL, Oracle, SQL Server, and MongoDB. However, this option does not address the requirements of MSP Bank, which include a managed relational database that can support both read and write workloads with a performance increase of up to 5 times the existing implementation.
Option F - Use Data Migration Service (DMS) and Schema Conversion Tool (SCT) to address migration of MySQL database on premise to database on AWS cloud: This option involves using the AWS Data Migration Service (DMS) and Schema Conversion Tool (SCT) to migrate the MySQL database to a managed relational database on AWS. SCT helps convert the database schema and application code to work with the new database engine. While this option provides a comprehensive migration solution, it does not address the requirement of a managed relational database that can support both read and write workloads with a performance increase of up to 5 times the existing implementation.
Therefore, the best options for MSP Bank to migrate their MySQL database to a managed relational database with performance of up to 5 times the existing implementation while supporting both read and write workloads without impacting the web application are options A and C.