3
Our reference architecture depicts a game backend that supports a
wide set of game features, including login, leaderboards, challenges,
chat, binary game data, user-generated content, analytics, and online
multiplayer capabilities. Keep in mind that not all games have all of
these components, but the following diagram provides a visualization
of how they would fit together. In this guide, we'll cover HTTP/JSON
servers and stateful game servers (labeled 2 and 4 in the diagram).
You can find more information about the other pieces of this reference
architecture in the Introduction to Scalable Game Development
Patterns on AWS.
Reference architecture for
a scalable game backend
1.0
Stateful Game Servers
Security Group
HTTP/JSON Servers Auto
Scaling Group
Stateful Game Servers
Security Group
HTTP/JSON Servers Auto
Scaling Group
Job Workers Auto
Scaling Group
ElastiCache for Redis
Security Group
CACHE
CACHE
Job results
Run job
SQS for job
queues
SNS for push
messages
Availability Zone A
Single Region (Oregon, Singapore, etc.)
Availability Zone B
CloudFront CDN
Elastic Load
Balancing
Game data
Reads Reads
Writes
Writes
RDS MySQL
Broadcast
message for
game
Queue
async
job
Mobile push
notifications
S3 for binary
game assets
TCP HTTP/S HTTP/S Stateful TCP socket
A fully production-ready
game backend on AWS
M
R R
S
Server
PUT
Client
GET
1
7
2
3
4
5
6 8
Learn how Behaviour Interactive uses our managed
service GameLift to scale its game servers.
