A gaming company runs a multiplayer platform with active players across North America, Europe, and Asia. Player state (inventory, progress) must be written and read with low latency in each region, and the application requires that writes in any region be acknowledged locally without waiting for a distant primary. The team wants a managed database design that keeps write latency low for all regions simultaneously. Which database design best meets this requirement?