Game Development Reference
In-Depth Information
Enterprise deployment architecture
The simple architecture works well if you are writing one game and your traffic
is around a few thousand players. But what if you are planning to write and
deploy tens or even hundreds of games? Then how would the server deployment
architecture look like that can sustain it?
Referring to the following figure you will notice a few things. There is more than one
game server; here each game server is responsible for handling all the events
for rooms belonging to a set of lobbies.
You will also notice there are a few other processes such as the session server and the
balancer. These processes assist game servers in keeping the load balanced among
the game servers, or in Session Server's case, take some of the load off the game
server. You will also notice that there is an additional DB called
Auth
DB
so that the
authentication traffic can be separated out from the game-related persistence traffic
hitting the database. The database itself may be scaled using clustering techniques
available in MySQL and other commercial products.
