Case Study: How No Man's Sky used Azure to share an infinite universe.
summary
No Man’s Sky shares discoveries and real-time play by using Azure App Service for platform as a service, Cosmos DB holding ~3 TB of JSON documents, Event Hub for ingestion, Key Vault for secrets, and PlayFab (matchmaking + Party) with a dual PlayFab networks design. Launch hits exhaust connection limits so teams scale VM types and autoscale; three separate ~2 TB databases merge via the change feed + Azure Functions. Migrations and cross‑play work; costs fall after Linux migration and PlayFab pricing changes.
AI-written summary · about
chapters (11)
- 0:00Azure for game creators
- 6:30No Man's Sky cloud needs
- 8:17Backend with App Service & Cosmos DB
- 11:06Five years of Azure growth
- 13:11Launch-day server load handling
- 16:19Cloud features for player engagement
- 18:27Porting to Xbox Series X|S
- 20:32Cross-platform player interactions
- 25:45Cross-play database merge
- 28:56Cloud journey key takeaways
- 30:19Azure gaming resources
related talks
57mArchitecture in the Azure Cloud
59mBuilding Resilient Applications In Microsoft Azure
55mCloud services for gaming
01h 00mBuilding Resilient Applications In Microsoft Azure
47mBuild scalable cloud-native apps with AKS and Azure Cosmos DB
59mRunning a real world, mission-critical system on Azure
23mThe Open Source Revolution: How Kubernetes is Changing the Games Industry
46mBuilt for billions, tailored for games; harnessing Google for serving players