Containerising Your Game Servers
summary
AWS Game Tech anatomy: Amazon GameLift runs session-based servers with FlexMatch and Fleet IQ (Fleet IQ can use spot capacity up to 90% discount), and container options include ECS/EKS/Fargate with images stored in ECR. Example repo shows Fargate + Cognito + API Gateway + Lambda + ElastiCache Redis routing players to container IPs; containers start fast and auto-shutdown after fixed games. Build tips: multi-stage builds, small base images and cache-friendly Dockerfile ordering cut image sizes from hundreds of MB to single digits.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:18AWS Global Infrastructure
- 3:10Amazon Gamelift
- 4:40Capacity Planning
- 6:04How Gamelift Works
- 7:27What is a Game Backend
- 9:25Benefits of Containers
- 11:14Game Package Services
- 12:26Container Services Overview
- 15:38Peak Games
- 17:02AWS Fargate
- 18:05Game Servers on AWS
- 18:57Solution Architecture
- 20:41Best Practices
- 21:45Image Size
- 26:04Multiple Environments
- 26:51Summary
related talks
55mCloud services for gaming
22mGiving Your Game the Best Chance of Success in the Cloud
43mBringing EDA to the Containers World
27mModernize your applications with serverless, containers, and Amazon EFS
51mArchitecting for Hyperscale with AWS: Navigating Real-world Serverless Challenges
49mServerless Architectural Patterns and Best Practices
01h 01mYou have a container image: Now what?
23mOn-demand Container Loading in AWS Lambda