Beating the Final Boss: Launch your game!

Transcription

1 Beating the Final Boss: Launch your game! Ozkan Can Solutions Architect,

2 ERROR The servers are busy at this time. Please try again later. (Error Code: 42 OOPS) Retry

3 READY FOR LAUNCH?! WORST-CASE SCENARIO x 50 PLAYERS APPSTORE FEATURING CUSTOMER RATINGS PRESS REVIEWS MARKETING PROMOTIONS SOCIAL MEDIA TIME

4 SCALE TO WHAT YOU NEED PAY FOR WHAT YOU USE Unmet Demand Upset Players Missed Revenue :( Servers Demand Capacity Demand Excess Capacity Wasted $$ Traditional: Rigid AWS: Elastic

5 ANTI-PATTERN - MONOLITH AUTHENTICATION MULTIPLAYER GAME LOGIC AI MATCH MAKING BI + ETL FRAUD DETECTION SHOP MODULE CHAT GAME DATA

6 ANTI-PATTERN MONOLITH SCALING AUTHENTICATION BI + ETL AUTHENTICATION BI + ETL FRAUD DETECTION FRAUD DETECTION MULTIPLAYER GAME LOGIC AI SHOP MODULE MULTIPLAYER GAME LOGIC AI SHOP MODULE MATCH MAKING CHAT MATCH MAKING CHAT GAME DATA GAME DATA

7 DECOUPLING AUTHENTICATION MULTIPLAYER GAME LOGIC AI MATCH MAKING BI + ETL FRAUD DETECTION SHOP MODULE CHAT GAME DATA

8 Service Oriented Architecture AUTHENTICATION HTTP(S) BI + ETL

9 Service Oriented Architecture AUTHENTICATION HTTP(S) AUTHENTICATION HTTP(S) BI + ETL Elastic Load Balancer AUTHENTICATION

10 Service Oriented Architecture AUTHENTICATION BI + ETL HTTP(S) AUTHENTICATION HTTP(S) BI + ETL Elastic Load Balancer AUTHENTICATION Elastic Load Balancer BI + ETL 200 TX/sec 50 TX/sec 50 TX/sec

11 Event-Driven Architecture HTTP(S) AUTHENTICATION AUTHENTICATION BI + ETL BI + ETL Elastic Load Balancer (ELB) AUTHENTICATION Amazon Simple BI + ETL Queue Service (SQS) 200 TX/sec 50 TX/sec

12 Event-Driven Architecture AUTHENTICATION BI + ETL v1.0 HTTP(S) AUTHENTICATION BI + ETL v2.0 Elastic Load Balancer (ELB) AUTHENTICATION Amazon Simple BI + ETL v3.0 Queue Service (SQS) 200 TX/sec 50 TX/sec

13 GLOBAL REACH

14 COMMON GAME BACKEND CONCEPTS Think in terms of APIs HTTP + JSON Get friends, leaderboard Binary asset data Multiplayer servers High availability Scalability

15 CORE (HA) GAME BACKEND Choose region >=2 Availability Zones Amazon EC2 for app Elastic Load Balancing Amazon Relational Database Service Multi-AZ ELB Region

16 SCALE IT OUT Amazon Simple Storage Service (S3) Game data Assets User-generated content Analytics ELB Region

17 AMAZON S3 Secure, durable, highly-scalable object storage. Store and retrieve any amount of data from anywhere on the web The flexibility of the AWS Cloud allows us to do things that we otherwise couldn t do. With AWS, we have tremendous flexibility, and we never get into a situation where there is something we can t do.

18 SCALE IT OUT Amazon S3 for game data Assets User-generated content Analytics Amazon Cloudfront ELB CloudFront CDN Region

19 AMAZON CLOUDFRONT Global CDN that accelerates delivery of your DLC, Update Patches, APIs, video content or other files. By combining the power of AWS compute & storage with the Amazon CloudFront content delivery network, we can provide an excellent user experience to everybody playing our games & watching our video content regardless of their geographical location, Sega didn't provide us a quote, but they do use CloudFront and they would have said some very nice things in this quote. You have to trust us on this!

20 SCALE IT WAY OUT Amazon S3 for game data Assets User-generated content Analytics Amazon CloudFront Auto Scaling Group Capacity on demand Respond to users Automatic healing ELB Region CloudFront CDN

21 SCALE IT WAY OUT Amazon S3 for game data Assets User-generated content Analytics Amazon CloudFront Auto Scaling Group Capacity on demand Respond to users Automatic healing Amazon ElastiCache Memcached & Redis ELB Region CloudFront CDN

22 WRITING IS PAINFUL Games are write heavy Caching of limited use Key-Value Binary structures Database = bottleneck ELB CloudFront CDN Region

23 SHARDING IS NOT FUN

24 AMAZON DYNAMODB Fully-managed NoSQL data store Provisioned throughput Secondary indexes PUT/GET keys TTL Eviction Document Support 400 KB Items Amazon DynamoDB Accelerator (Cache) ELB CloudFront CDN Region

25 EXAMPLE: LEADERBOARD IN DYNAMODB UserID (hash key) BoardName (range key) TopScore TopScoreDate "101" "Galaxy Invaders" 5842 " T17:24:31" "101" "Meteor Blasters" 1000 " T23:18:01" "101" "Starship X" 24 " T13:14:21" "102" "Alien Adventure" 192 " T11:07:56" "102" "Galaxy Invaders" 0 " T07:33:42" "103" "Attack Ships" 3 " T01:13:24" "103" "Galaxy Invaders" 2317 " T06:53:00" "103" "Meteor Blasters" 723 " T01:14:24" "103" "Starship X" 42 " T06:53:03" Hash key = Primary key Range key = Sub key Range key = Sort key Others attributes are undefined So How to sort based on Top Score?

26 SECONDARY INDEXES UserID (hash key) BoardName (range key) TopScore TopScoreDate "101" "Galaxy Invaders" 5842 " T17:24:31" 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 cases BoardName (hash key) TopScore (range key) UserID "Alien Adventure" 192 "101" "Attack Ships" 3 "103" "Galaxy Invaders" 0 "102" "Galaxy Invaders" 2317 "103" "Galaxy Invaders" 5842 "101" "Meteor Blasters" 723 "103" "Meteor Blasters" 1000 "101" "Starship X" 24 "101" "Starship X" 42 "103"

27 DYNAMODB DOCUMENTS Scalar types: String, Number, Binary, Boolean, Null Multi-value types: String Set, Number Set, Binary Set Document types: List, Map Document content addressing "name": TerryCrews", "games": ["Megablast", "Spacerace"], "score": { "Megablast" : 123, "Spacerace" : 41 } document.score.megablast "name": { "S": "Martin" } "games": { "L": [ { "S": "Megablast" }, { "S": "Spacerace" } ] }, "score": { "M": { "Megablast": { "N": "123" }, "Spacerace": { "N": "41" } } }

28 AMAZON DYNAMODB Fully managed NoSQL database with single digit latency at any scale Using Amazon DynamoDB frees us from building, maintaining, & sharding large real-time data intensive projects. By using AWS, Frontier Games can scale compute resources easily to handle large spikes in user traffic with popular titles, and is saving up to 30 percent compared to using a traditional technology infrastructure,

29 MULTIPLAYER GAME SERVERS API backend app Core session Matchmaking S3+CloudFront DLC, assets Game saves User-generated content Public server tier Direct client socket Scale on players Region

30 MULTIPLAYER GAME SERVERS 1 Login via API 2 Request matchmaking 3 Get game server IP Region

31 MULTIPLAYER GAME SERVERS 1 Login via API 2 Request matchmaking 3 Get game server IP 4 Connect to server 5 Pull down assets 6 Other players join Region

32 Region B Region A

33 PRE-LAUNCH CHECKLIST SECURITY IS JOB ZERO Design for failure Consider Service Limits Monitor everything Consider data access patterns Decommission unused resources Plan for unplanned events: AWS Support Read the Well-Architected Framework Whitepaper Schedule a Well-Architected Review with your AWS account team

34 Focus on your players!

35 Infrastructure is not a differentiator.

36 Don t limit yourself by technology.

37

38 BEGIN YOUR JOURNEY WITH AWS!