Question

A gaming company runs a multiplayer backend as a set of stateless microservices on Azure. Players are distributed across North America, Europe, and Asia. Currently all traffic routes to a single region in East US, and players in Asia experience high write latency because game state updates must travel to East US. The architects want each region to accept local writes with low latency while keeping data eventually synchronized globally. Which architectural approach should you recommend?

Accepted Answer

Deploy the microservices to multiple regions and back them with an Azure Cosmos DB account configured for multi-region writes, following the Geode pattern.

Answer

Keep a single deployment in East US but place Azure Front Door in front of it to accelerate write requests from Asia.

Answer

Deploy the microservices to multiple regions but keep a single Azure SQL Database in East US as the primary write endpoint for all regions.

Answer

Deploy the microservices to a single region and add Azure Cache for Redis in each region to buffer writes locally.