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.

Lessons Learned and Best Practices for Game Development in the Cloud

664 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.

Published in: Technology, Business

Lessons Learned and Best Practices for Game Development in the Cloud

  1. 1. LESSONS LEARNED
  2. 2. LESSONS LEARNEDand best practices for game developersin the cloud.@sarahnovotny
  3. 3. INTRODUCTION TOwe do video game transmedia
  4. 4. TRANSMEDIAtransmedia is thetechnique of telling asingle story or storyexperience acrossmultiple platforms andformats using currentdigital technologies.
  5. 5. WHY THE CLOUDS?or more specifically, why ?
  6. 6. flickr @nishanthjois
  7. 7. BUSINESS CONSTRAINTS->ARCHITECTURAL CONSTRAINTS(no really, they’re helpful)
  8. 8. FREE TO PLAYanyone can playnot everyone will paycan’t be viewed as P2W
  9. 9. GAME SERVERephemeralautomatedinstrumentedcheap
  10. 10. BUZZWORD COMPLIANTcloudon demand resourcesAPI driven$0 capital investment
  11. 11. WHAT HAVE WELEARNED?robots and automation FTW!
  12. 12. Availability Zone #1www.playhawken.comSecurity GroupRoot VolumeData VolumeElastic Load BalancerWebserver InstancesWeb AppServerSecurity GroupProxy InstancesDynamo BackendElastic IP3rd PartyServices
  13. 13. Availability Zone #1HAWKEN game playGame ServerInstancesDynamo BackendAvailability Zone #2S3 BucketGame Client DistributionGame ServiceInstances
  14. 14. THINK IN TERMS OF FLEETSone server is useful. a fleet of them is a product.
  15. 15. SCALING UP IS EASY
  16. 16. SCALING DOWN IS HARD
  17. 17. BUILD AWARENESSapplicationautomation
  18. 18. LOCATION
  19. 19. APIS OFFER ERROR CODES200 OK201 Created202 Accepted204 No Content304 Not Modified400 Bad Request403 ForbiddenCHECKTHEM
  20. 20. PLAN FOR THE
  21. 21. ASYNCHRONICITYdon’t assume the data you’ve just sent is where you’ll retrieve it
  22. 22. CULTURElegacy thinkingeducationeducationeducationengineering leadershippatienceBIZDEVCLOUDDEVhere bedragons
  23. 23. COMPLEXITY KILLSnot too hotnot too coldjust right
  24. 24. I’M @sarahnovotny& YES, I’M HIRING
  25. 25. We are sincerely eager tohear your feedback on thispresentation and on re:Invent.Please fill out an evaluationform when you have achance.

×