An online gaming studio is migrating its platform to the AWS Cloud. The migration team is evaluating two specific workloads:
1. A multiplayer matchmaking system that is currently a legacy monolithic application. The studio plans to completely rewrite this application to leverage a serverless, microservices-based architecture for dynamic scaling.
2. A player profiles database currently running on an on-premises PostgreSQL server. The studio wants to move this database to a managed cloud database service to reduce administrative overhead, without changing the database engine or the database schema.
Which of the following migration strategies should the studio select for these workloads? (Select TWO.)
- Refactoring (Re-architecting) for the multiplayer matchmaking systemAnswer
- Replatforming for the player profiles databaseAnswer
- CRehosting for the multiplayer matchmaking system
- DRepurchasing for the player profiles database
- ERetaining for the multiplayer matchmaking system
Answer
Refactoring (Re-architecting) for the multiplayer matchmaking system, and Replatforming for the player profiles database.
Refactoring (Re-architecting) is correct for the matchmaking system because it involves rewriting the application code to implement a microservices-based, serverless architecture. Replatforming is correct for the player profiles database because the database is moved to a managed cloud database service (like Amazon RDS) to minimize administrative overhead while preserving the original database engine and schema.
Step-by-Step Solution
Key Concept
AWS Cloud Migration Strategies (6 Rs)