A global online gaming company is launching a new massively multiplayer online (MMO) game. The game backend needs to store player profiles, game state, and leaderboard data. This data requires extremely low-latency reads and writes (single-digit milliseconds), must handle millions of concurrent users and requests per second, and needs to scale globally across multiple regions to ensure a seamless experience for players worldwide. Data consistency can be eventually consistent for most game state updates. Which database service should a solutions architect recommend?

Why the other options are wrong

• A. RDS with read replicas offers read scaling but lacks the active-active write capabilities across regions and the extreme scalability for millions of requests per second with single-digit millisecond latency required for global MMOs.
• B. Aurora Global Database is excellent for relational workloads and fast cross-region replication, but DynamoDB is generally better suited for the extreme scale, low-latency, and flexible consistency requirements of MMO game data.
• D. ElastiCache for Redis is an in-memory data store, excellent for caching and session management, but it is not a primary persistent database for storing core player profiles and game state across regions with high durability requirements.