Question

A company runs a Java monolith on self-managed Apache Tomcat instances in an on-premises data center, backed by a self-managed MySQL 5.7 database. The migration mandate requires reducing operational overhead of the OS, application server patching, and database administration without rewriting application code. The team also wants to complete the migration within a tight 3-month window and cannot afford a full re-architecture. Which migration approach best satisfies these requirements?

Accepted Answer

Replatform by packaging the Java application into containers running on Amazon ECS with AWS Fargate, and migrate the MySQL database to Amazon RDS for MySQL using AWS DMS.

Answer

Rehost the Tomcat instances to EC2 using AWS Application Migration Service (MGN) and lift-and-shift MySQL onto EC2 with self-managed replication for failover.

Answer

Refactor the monolith into microservices deployed on AWS Lambda behind Amazon API Gateway, and migrate the data to Amazon DynamoDB with a new access pattern design.

Answer

Repurchase by replacing the custom Java application with a commercial SaaS offering and export the MySQL data to the vendor's managed platform.