Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

GMG203 Meteor Entertainment’s Lessons Learned and Best Practices for Game Developers - AWS re: Invent 2012

1,171 views

Published on

Game developers need to spend their time building new games and features, not managing infrastructure. Meteor Entertainment has learned how-to minimize the time they spend managing infrastructure by automating deployments, monitoring systems through log analysis, and by making their data tier easy to scale. Attend this session to hear all about Meteor’s best-practices.

  • Be the first to comment

  • Be the first to like this

GMG203 Meteor Entertainment’s Lessons Learned and Best Practices for Game Developers - AWS re: Invent 2012

  1. 1. we do video game transmediaINTRODUCTION TO
  2. 2. transmedia is theTRANSMEDIA technique of telling a single story or story experience across multiple platforms and formats using current digital technologies.
  3. 3. or more specifically, why ?WHY THE CLOUDS?
  4. 4. flickr @nishanthjois
  5. 5. (no really, they’re helpful)BUSINESS CONSTRAINTS->ARCHITECTURAL CONSTRAINTS
  6. 6. anyone can playnot everyone will paycan’t be viewed as P2WFREE TO PLAY
  7. 7. ephemeralautomatedinstrumentedcheapGAME SERVER
  8. 8. cloudon demand resourcesAPI driven$0 capital investmentBUZZWORD COMPLIANT
  9. 9. robots and automation FTW!WHAT HAVE WELEARNED?
  10. 10. www.playhawken.com Elastic IP 3rd Party Services Proxy Instances Security Group Web App Server Elastic Load Balancer Webserver Instances Security Group Dynamo Backend Data Volume Root Volume Availability Zone #1
  11. 11. HAWKEN game play Game Server Instances Game Client Distribution Dynamo Backend Game Service Instances Availability Zone #1 S3 Bucket Availability Zone #2
  12. 12. one server is useful. a fleet of them is a product.THINK IN TERMS OF FLEETS
  13. 13. SCALING UP IS EASY
  14. 14. SCALING DOWN IS HARD
  15. 15. BUILD AWARENESS automation application
  16. 16. LOCATION
  17. 17. 200 OK201 Created202 Accepted CHECK204 No Content THEM304 Not Modified400 Bad Request403 ForbiddenAPIS OFFER ERROR CODES
  18. 18. PLAN FOR THE
  19. 19. don’t assume the data you’ve just sent is where you’ll retrieve itASYNCHRONICITY
  20. 20. BIZlegacy thinkingeducationeducation here beeducation dragons CLOUDDEVengineering leadershippatienceCULTURE DEV
  21. 21. not too hotnot too coldjust rightCOMPLEXITY KILLS
  22. 22. I’M @sarahnovotny & YES, I’M HIRING
  23. 23. We are sincerely eager to hear your feedback on thispresentation and on re:Invent. Please fill out an evaluation form when you have a chance.

×