Gaming scenarios
For our gaming architectures, we're launching from our basic data discussions in Chapter 6, Data Architecture. We have three architectures that span two important gaming scenarios. First, we achieve low latency with a LAMP architecture. Then we'll look at two architectures that provide different perspectives (open source and full service) on data architecture for the gaming industry.
Low-latency multiplayer gaming
First, you'll explore the open source LAMP architecture, which stands for a specific stack: a Linux Ubuntu VM (L), Apache web server (A), MySQL (M), and PHP (P). Azure Load Balancer gives the client the IP address from the DNS. The VMs read info from Azure Cache for Redis and read/write to/from Azure Database for MySQL.
More information
This architecture provides robust instructions on calculating the associated costs:
LAMP Gaming Reference Architectures: https://docs.microsoft.com/gaming/azure/reference-architectures/general...
