Lessons Learned and Best Practices for Game Developers in the Cloud
•Download as PPTX, PDF•
2 likes•791 views
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.
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (20)
Similar to Lessons Learned and Best Practices for Game Developers in the Cloud
Similar to Lessons Learned and Best Practices for Game Developers in the Cloud (20)
More from sarahnovotny
More from sarahnovotny (15)
Recently uploaded
Recently uploaded (20)
Lessons Learned and Best Practices for Game Developers in the Cloud
- 2. LESSONS LEARNED and best practices for game developers in the cloud. @sarahnovotny
- 3. INTRODUCTION TO we do video game transmedia
- 4. TRANSMEDIA transmedia is the technique of telling a single story or story experience across multiple platforms and formats using current digital technologies.
- 6. WHY THE CLOUDS? or more specifically, why ?
- 9. BUSINESS CONSTRAINTS-> ARCHITECTURAL CONSTRAINTS (no really, they’re helpful)
- 10. FREE TO PLAY anyone can play not everyone will pay can’t be viewed as P2W
- 12. BUZZWORD COMPLIANT cloud on demand resources API driven $0 capital investment
- 13. WHAT HAVE WE LEARNED? robots and automation FTW!
- 14. Availability Zone #1 www.playhawken.com Security Group Root VolumeData Volume Elastic Load Balancer Webserver Instances Web App Server Security Group Proxy Instances Dynamo Backend Elastic IP 3rd Party Services
- 15. Availability Zone #1 HAWKEN game play Game Server Instances Dynamo Backend Availability Zone #2 S3 Bucket Game Client Distribution Game Service Instances
- 16. THINK IN TERMS OF FLEETS one server is useful. a fleet of them is a product.
- 17. SCALING UP IS EASY
- 18. SCALING DOWN IS HARD
- 20. LOCATION
- 21. APIS OFFER ERROR CODES 200 OK 201 Created 202 Accepted 204 No Content 304 Not Modified 400 Bad Request 403 Forbidden CHECK THEM
- 22. PLAN FOR THE
- 23. ASYNCHRONICITY don’t assume the data you’ve just sent is where you’ll retrieve it
- 24. CULTURE legacy thinking education education education engineering leadership patience BIZ DEV CLOUDDEV here be dragons
- 25. COMPLEXITY KILLS not too hot not too cold just right
- 26. I’M @sarahnovotny & YES, I’M HIRING
- 27. We are sincerely eager to hear your feedback on this presentation and on re:Invent. Please fill out an evaluation form when you have a chance.
Editor's Notes
- timing. when I was brought on, we had 345 days and no infrastructure