I recently ran across a Quora discussion from a few years ago about the technology stack of Ultima Online’s original servers. In it, a few of the game’s developers recall some of the game’s early server architecture decisions and their outcomes. It’s an interesting read with some good real-life insights.
The game design seeks to create engaging game play within fixed technical and resource constraints. It trades game play features against number of concurrent players, player immersion, and size or complexity of the game world to simplify implementation, deployment, and maintenance. Continue reading Pattern: Monolithic Architecture
This page presents a collection of multiplayer game server architecture patterns that describe solutions to common problems in multiplayer game server development. Over time, I hope to build a library of patterns based on real-world experience, research and experimentation by game server developers.
A description of the Monolithic Architecture pattern as it applies to multiplayer game server architecture.
Use the Distributed Network Connections pattern to maximize the number of connected clients with minimal impact on game server performance.
Problem How do we ensure a balanced distribution of client connections across a set of connection servers in a distributed game server architecture? Context We are developing the server for a massively multiplayer online game with a client-server architecture. The game design seeks to create an immersive play experience by enabling thousands of players to connect simultaneously … Continue reading Pattern: Client Side Load Balancing
Problem How do we distribute the load of running core game play functionality across multiple processes to support thousands of concurrent players? Context We are developing the server for a massively multiplayer online game with a client-server architecture. The game design seeks to create an immersive play experience by enabling thousands of players to interact with each other in a … Continue reading Pattern: Map-Centric Game Server
Problem How do we distribute core game play load across multiple processes in a way that supports flexible scaling and efficient allocation of computing resources? Context We are developing the server for a massively multiplayer online game with a distributed architecture. The game design seeks to create an immersive play experience by enabling thousands of players to interact … Continue reading Pattern: Responsibility-Oriented Game Server
Problem How do we create a game server that permits unlimited freedom of movement and game play on an expansive map with no apparent boundaries? Context We are developing the server for a massively multiplayer online game with a client-server architecture. The game design seeks to create an immersive play experience by enabling thousands of players to interact with … Continue reading Pattern: Seamless World Game Server
If you have feedback, corrections, or questions about any of the patterns you see at Engines of Delight, please leave a comment on this page, or any of the specific pattern posts.
Simon Brown, author of Software Architecture for Developers, talks with Sven Johann about using Software Architecture Sketches to visualize, communicate and document software architecture. Continue reading [Podcast] SE Radio: Software Architecture Sketches with Simon Brown
Micro services is an emerging trend in software architecture that focuses on small, lightweight applications as a means to avoid large, unmaintainable, monolithic systems. Continue reading [Podcast] SE Radio: Stefan Tilkov on Architecture and Micro Services
Carl and Richard talk to Marc Mercuri and Mark Simms about resilient cloud architecture. The conversation starts out focused on the white paper called ‘FailSafe’ and the guidance it provides for building resilient cloud applications – but the information is applicable to any large scale system running on any sort of infrastructure. Continue reading [Podcast] DotNetRocks: Marc Mercuri and Mark Simms Build Resilient Cloud Applications
In an earlier post I described some multiplayer game types and identified several clues about the server architecture required to build each type. Now I want to take a closer look at some of those clues to see how they can help us know what to build. Continue reading Know what to Build: Assessing Impacts
I have a Seiko analog watch that needs repair. When I pull out the crown to set the time, the movement stops. This is normal. But when I push the crown back in, the movement doesn’t resume right away. It sometimes takes several minutes for it to start ticking again.
I love this watch. My wife gave it to me for our anniversary years ago, and I’ve worn it daily ever since. I’m definitely going to have it repaired. Administrivia isn’t my strong suit, though, so I haven’t gotten around to it yet.
Meanwhile, I keep wearing it. I’ve learned that if I just stop messing with it, I can still rely on it to keep time. Now, I just remember the offset between the actual time and my watch’s time and do the head math. This works because the watch is consistent, and I’ve become consistent in using it this way. Continue reading Consistency FTW!
Software is a solution to some problem. As I’ve already said, software architecture is the foundation on which we build our software. It’s at the core of the solution we offer in any software we build. Continue reading Know what to Build: Multiplayer Game Types