Soru

Zorluk: ZorAssess and Select Migration Strategy (7 Rs)

A company is planning to migrate a legacy document processing application to AWS within a strict 6-month timeline. The application consists of three tiers:

1. A web tier running Apache HTTP Server on Red Hat Enterprise Linux 7 virtual machines.
2. A processing tier running a Java-based document parsing engine on IBM AIX servers. The engine utilizes a proprietary native C-shared library for file parsing and requires POSIX-compliant local filesystem access. The company cannot rewrite the core logic due to budget and time constraints.
3. A database tier running Oracle Database 19c on-premises, using proprietary Oracle Spatial features for document metadata geotagging. The company wants to eliminate commercial database licensing costs and is willing to convert the database schema and modify application SQL queries.

Which combination of migration strategies (7 Rs) represents the most appropriate and feasible migration path for this application?

  1. Rehost the web tier on Amazon EC2 using AWS Application Migration Service (MGN); Replatform the processing tier by recompiling the C-shared library and running the Java application on x86_64 Amazon Linux 2 EC2 instances; Refactor the database tier by converting the Oracle schema and migrating to Amazon Aurora PostgreSQL using the AWS Schema Conversion Tool (SCT) and AWS Database Migration Service (DMS).Cevap
  2. B
    Rehost the web tier on Amazon EC2 using AWS Application Migration Service (MGN); Rehost the processing tier on Amazon EC2 using AWS Application Migration Service (MGN); Replatform the database tier to Amazon Aurora PostgreSQL using AWS Schema Conversion Tool (SCT) and AWS Database Migration Service (DMS).
  3. C
    Rehost the web tier on Amazon EC2 using AWS Application Migration Service (MGN); Replatform the processing tier by running the Java application on x86_64 Amazon Linux 2 EC2 instances; Replatform the database tier to Amazon Aurora PostgreSQL using AWS Database Migration Service (DMS) to minimize code changes.
  4. D
    Replatform the web tier by containerizing the Apache server on Amazon ECS; Refactor the processing tier by rewriting the core Java logic and POSIX file operations to use AWS Lambda and Amazon S3; Rehost the database tier to Amazon RDS for Oracle.

Cevap

Rehost the web tier on Amazon EC2 using AWS Application Migration Service (MGN); Replatform the processing tier by recompiling the C-shared library and running the Java application on x86_64 Amazon Linux 2 EC2 instances; Refactor the database tier by converting the Oracle schema and migrating to Amazon Aurora PostgreSQL using the AWS Schema Conversion Tool (SCT) and AWS Database Migration Service (DMS).
The correct strategy involves rehosting the web tier, replatforming the processing tier, and refactoring the database tier. Rehosting the web tier using AWS Application Migration Service (MGN) is the fastest way to migrate the RHEL 7 virtual machines within the 6-month timeline. The processing tier runs on IBM AIX, which uses the POWER architecture. Because AWS MGN only supports block-level replication for x86/x64 Windows and Linux, the workload cannot be rehosted directly. Replatforming is the correct choice here because the Java application and C-shared library must be ported and recompiled to run on x86_64 Amazon Linux 2 EC2 instances, preserving the local POSIX filesystem behavior without rewriting the core application logic. The database tier must be refactored because moving from Oracle Database to Amazon Aurora PostgreSQL is a heterogeneous database migration that requires schema conversion (using the AWS Schema Conversion Tool) and database query rewrites (specifically for the proprietary Oracle Spatial features to PostGIS), which constitutes a Refactor strategy.

Adım Adım Çözüm

1
Analyze the web tier migration requirements.
The web tier runs on Red Hat Enterprise Linux 7, which is fully supported for block-level replication by AWS Application Migration Service (MGN), making Rehost the most efficient choice within the 6-month timeline.
Identifying the quickest, lowest-risk migration path for compatible virtual machines helps meet tight schedule constraints.
2
Evaluate migration options for the proprietary IBM AIX processing tier.
AWS MGN cannot be used because it does not support AIX (POWER architecture). Because the application cannot be rewritten due to budget, but must run on x86_64 EC2, we must recompile the native C-shared library and package the Java application for Linux. This is classified as a Replatform strategy.
Determining OS compatibility and matching it against workload constraints prevents infeasible migration pathways.
3
Assess the database tier migration path.
Moving from Oracle to Amazon Aurora PostgreSQL is a heterogeneous database engine migration. Because the application utilizes proprietary features (Oracle Spatial) that must be converted (e.g., to PostGIS) and SQL queries must be modified, this requires AWS SCT and DMS, which falls under the Refactor (Re-architect) migration strategy.
Distinguishing between a minor database migration (RDS Oracle - Replatform) and a complete database engine change with code modification (Refactor) ensures correct resource allocation and planning.

Anahtar Kavram

Assess and Select Migration Strategy (7 Rs)
Tahmini Süre:3m 0s
Bu soruyu puanla