An important factor we’ve focused on when managing GATM has been keeping the website and game server on different platforms. The main purpose for this has been simple: performance.
We keep the website on a shared hosting account and the game servers on our dedicated server. Believe it or not, websites are resource hogs… especially high traffic ones. Every time someone loads up a page from your site, all the content including images needs to be accessed and sent over to the user. And that’s not even mentioning MySQL. If you have something running a database (i.e. a blog or forums) not only does the previously mentioned stuff happen, but then the MySQL server has to perform a query (or maybe even 10 queries, depending on what you’re doing).
So start taking that into account every time you hit refresh on a forum page, or quickly browse through pages of a post. There’s a lot of shit going on behind the scenes. And we wouldn’t want all that affecting the experience of those in our servers.
Now that you understand why we keep them separated, there’s one other issue. How do you communicate between the two? This is a major part of our task because people like seeing the integration of game server and website/forum. For the stability of the games, we keep the game data local to the server. WHRY? Simple answer is simple: you never want the game server dependent on ANYTHING. If the data is stored on the website and the website takes a shit… what happens? Yup… the game server takes a shit too, and you have a possibility of lost data.
Overcoming this obstacle isn’t all that hard, but the solution can’t bring down resources on the game server as I spoke about earlier. I’ll explain how we do this later.
0 Responses to “Website and game server ballet”