In this session, AWS shares best practices for mobile, console, and MMO games that can scale from 1,000 to 1,000,000 users. See how to create a game backend using Amazon EC2 and AWS Elastic Beanstalk. Learn about database scaling challenges, and how to use Amazon DynamoDB and Amazon ElastiCache to address them. And, hear how to deliver game assets efficiently using Amazon S3 and Amazon CloudFront. Then, hear from Roope Kangas, Lead Server Developer and co-founder at Grand Cru, about their journey launching and cost-optimizing Supernauts on AWS. Grand Cru used load testing to validate their system before launch, enabling them to reach 1 million users in 6 days. Then, after launch, the team optimized their architecture based on system metrics to cut their AWS costs by more than half.

3. Traditional: Rigid
AWS: Elastic
Servers
Demand
Capacity
Excess Capacity Wasted $$
Demand
Unmet Demand
Upset Players
Missed Revenue :(

4. 11 Regions
52 Edge Locations
Continuous Expansion

5. Multiplayer
Leaderboards
Multi-platform
Achievements
Power-ups
In-game purchases
Multi-ball
Break-out mode

7. ELB
•Choose region
•>=2 AvailabilityZones
•Amazon EC2 for app
•Elastic Load Balancing
•Amazon RDS database
•Multi-AZ
Region

8. ELB
•Amazon S3 for game data
•Assets
•UGC
•Analytics
Region

9. ELB
•Amazon S3 for game data
•Assets
•UGC
•Analytics
•... with CloudFront!
Region
CloudFront
CDN

10. •Amazon S3 for game data
•Assets
•UGC
•Analytics
•... with CloudFront!
•Auto Scaling Group
•Capacity on demand
•Respond to users
•Automatic healing
ELB
Region
CloudFront
CDN

11. • Amazon S3 for game data
• Assets
• UGC
• Analytics
• ... with CloudFront!
• Auto Scaling Group
• Capacity on demand
• Respond to users
• Automatic healing
• Amazon ElastiCache
• Memcached
• Redis
ELB
Region
CloudFront
CDN

12. •Games are write heavy
•Caching of limited use
•Key value key value
•Binary structures
•Database = bottleneck
ELB
Region
CloudFront
CDN

13. (not fun)

14. •Fully-managed
•NoSQLdata store
•Provisioned throughput
•Secondary indexes
•PUT/GET keys
•Document Support!
•400 KB Items
•Reindexing(Soon!)
•Auto Scaling (OSS)
ELB
Region
CloudFront
CDN

15. •Hash key = Primary key
•Range key = Sub key
•Range key = Sort key
•Others attributes are undefined
•So… How to sort based on Top Score?
UserID(hash key)
BoardName(rangekey)
TopScore
TopScoreDate
"101"
"GalaxyInvaders"
5842
"2014-09-15T17:24:31"
"101"
"Meteor Blasters"
1000
"2014-10-22T23:18:01"
"101"
"StarshipX"
24
"2014-08-31T13:14:21"
"102"
"AlienAdventure"
192
"2014-07-12T11:07:56"
"102"
"GalaxyInvaders"
0
"2014-09-18T07:33:42"
"103"
"Attack Ships"
3
"2014-10-19T01:13:24"
"103"
"GalaxyInvaders"
2317
"2014-09-11T06:53:00"
"103"
"Meteor Blasters"
723
"2014-10-19T01:14:24"
"103"
"StarshipX"
42
"2014-07-11T06:53:03"

16. •Create a secondary index!
•Set hash key to BoardName
•Set range key to TopScore
•Project extra attributes as needed
•Can now query by BoardName, Sorted by TopScore
•Handles many common gaming use case
BoardName(hash key)
TopScore(rangekey)
UserID
"AlienAdventure"
192
"101"
"Attack Ships"
3
"103"
"GalaxyInvaders"
0
"102"
"GalaxyInvaders"
2317
"103"
"GalaxyInvaders"
5842
"101"
"Meteor Blasters"
723
"103"
"Meteor Blasters"
1000
"101"
"StarshipX"
24
"101"
"StarshipX"
42
"103"
UserID(hash key)
BoardName(rangekey)
TopScore
TopScoreDate
"101"
"GalaxyInvaders"
5842
"2014-09-15T17:24:31"

17. •Document types: List, Map
•Document content addressing
"name": "Martin",
"games": ["Megablast",
"Spacerace"],
"score": {
"Megablast" : 123,
"Spacerace" : 41
}
"name": {
"S": "Martin"
}
"games": {
"L": [ { "S": "Megablast" },
{ "S": "Spacerace" } ]
},
"score": {
"M": {
"Megablast": { "N": "123" },
"Spacerace": { "N": "41" }
}
}
,Boolean, Null
document.score.Megablast

18. SOV204
Scaling Up to Your First 10 Million Users
SDD407
Amazon DynamoDB: Data Modeling and Scaling Best Practices
GAM302
EA's Real-World Hurdles with Millions of Players in theSimpsons: Tapped Out

19. Region
•API backend app
•Core session
•Matchmaking
•S3+CloudFront
•DLC, assets
•Game saves
•UGC
•Public server tier
•Direct client socket
•Scale on players

20. ①Login via API
②Request matchmaking
③Get game server IP
Region

21. ①Login via API
②Request matchmaking
③Get game server IP
④Connect to server
⑤Pull down assets
⑥Other players join
Region

22. Region A
Region B

23. GAM402
Deploying a Low-Latency Multiplayer Game Globally: Loadout
GAM404
Gaming DevOps: Scopely'sContinuous Deployment Pipeline
GAM405
Create Streaming Game Experiences with Amazon AppStream

39. Load test environment
Metrics tools

40. 0 20 40 60 80
0 5000 10000 15000 20000 25000 30000
Engine Ping
Minutes
Milliseconds
ccu
95th
max
median
min
0 20 40 60 80
0 5000 10000 15000 20000 25000 30000
Join OK
Minutes
Milliseconds
ccu
95th
max
median
min
0 20 40 60 80
0 5000 10000 15000 20000 25000 30000
Spawn OK
Minutes
Milliseconds
ccu
95th
max
median
min
0 20 40 60 80
0 5000 10000 15000 20000 25000 30000
Turf API
Minutes
Milliseconds
ccu
95th
max
median
min
bad

41. 0 20 40 60 80 100
0 20000 40000 60000 80000
Engine Ping
Minutes
Milliseconds
ccu
95th
max
median
min
0 20 40 60 80 100
0 20000 40000 60000 80000
Join OK
Minutes
Milliseconds
ccu
95th
max
median
min
0 20 40 60 80 100
0 20000 40000 60000 80000
Spawn OK
Minutes
Milliseconds
ccu
95th
max
median
min
0 20 40 60 80 100
0 20000 40000 60000 80000
Turf API
Minutes
Milliseconds
ccu
95th
max
median
min
Better!

49. GAM303
Beyond Game Servers: Load Testing, Rendering, and Cloud Gaming
WEB306
UI, Load, and Performance Testing Your Websites on AWS
GAM301
Real-Time Game Analytics with Kinesis, Redshift, and DynamoDB
GAM304
How Riot Games re:Inventedtheir AWS Model
ARC302
Running Lean Architectures: How to Optimize for Cost Efficiency

50. wow
so managed
much gaming
such available
very scaling

51. Please give us your feedback on this session.
Complete session evaluations and earn re:Invent swag.
http://bit.ly/awsevals