Multiplayer Server Scaling with Azure Container Instances
- 11. File Table
- 13. ACICreate ACIDelete ACIList ACIDetails ACISetSessions ACISetState ACIMonitor ACIGC ACIAutoScaler
- 14. ContainerGroup 2 State: MarkedForDeletion ActiveSessions: 0 IP: 2.3.4.5 Azure Container Instances Infrastructure ContainerGroup 1 State: Creating ActiveSessions: 0 • No Container Instances exist • ACICreate is called • When deployment is complete, Azure Event Grid calls ACIMonitor and State is updated to Running • Users connect to ContainerGroup 1 • ACICreate is called manually OR ACIAutoScaler runs, the scale-out threshold has been crossed, calls ACICreate to create a second instance • When deployment is complete, Event Grid calls ACIMonitor so State is updated to Running • Users connect to ContainerGroup 2 • Eventually, the threshold for scale-in is crossed, and ContainerGroup 2 is no longer needed • ACISetState is called manually OR ACIAutoScaler runs, calls ACISetState. So, ContainerGroup 2 state is now MarkedForDeletion • All users disconnect from ContainerGroup 2 when game completes • ACIGC runs, ACIDelete is called and removes ContainerGroup 2 ContainerGroup 1 State: Running ActiveSessions: 0 IP: 1.2.3.4 ContainerGroup 2 State: Creating ActiveSessions: 0 ContainerGroup 2 State: Running ActiveSessions: 0 IP: 2.3.4.5 ContainerGroup 1 State: Running ActiveSessions: 8 IP: 1.2.3.4 ContainerGroup 2 State: Running ActiveSessions: 5 IP: 2.3.4.5 ContainerGroup 2 State: Running ActiveSessions: 2 IP: 2.3.4.5 ContainerGroup 2 State: MarkedForDeletion ActiveSessions: 2 IP: 2.3.4.5 ContainerGroup 2 State: MarkedForDeletion ActiveSessions: 0 IP: 2.3.4.5
- 16. Demo