An online gaming portal manages player matchmaking and game lobby orchestration. The current architecture relies on a single monolithic server to run the matchmaking logic, store active session states, and send notification emails to players when a match is found. During peak tournament events, the system struggles to handle the load, resulting in delayed notifications and failed match setups. To align with AWS Cloud design principles, which of the following architectural changes should the portal implement? (Select TWO.)
- Use Amazon DynamoDB to externalize session state, allowing the matchmaking compute components to operate statelessly and scale independently.Answer
- Migrate the email notification subsystem to Amazon Simple Notification Service (Amazon SNS), leveraging a managed service instead of maintaining custom mail server software.Answer
- CDeploy the monolithic matchmaking server on a single, highly-configured Amazon EC2 instance that remains running continuously to handle maximum potential user connections.
- DStore session states in the local memory of the matchmaking server and use sticky sessions to bind each player to that specific instance.
- EConfigure a secondary duplicate monolithic server in a cold standby state and manually update its configuration files whenever a game update is released.
Answer
The portal should implement using Amazon DynamoDB to externalize session state for stateless compute scaling and migrating the email notification subsystem to Amazon Simple Notification Service (Amazon SNS) to leverage managed services.
The correct architecture uses Amazon DynamoDB to store matchmaking session data externally, allowing the application tier to operate statelessly and scale horizontally (implementing loose coupling). It also utilizes Amazon SNS as a managed messaging service to handle notifications, removing the operational burden of managing a dedicated mail server (implementing services not servers).
Step-by-Step Solution
Key Concept
AWS Cloud Design Principles