1 / 20

Crafting the Ideal SpyParty Multiplayer Beta Server Architecture

Learn about the goals and components of SpyParty's beta infrastructure, focusing on a polished, secure, scalable, and flexible server architecture. Explore the importance of single sign-on, personalized beta homepages, security measures, and the use of Amazon AWS and other services. Dive into the considerations for load balancing, incremental rollouts, and flexibility in the infrastructure development process.

jamesbowman
Download Presentation

Crafting the Ideal SpyParty Multiplayer Beta Server Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Not Waving but Drowning SpyParty Multiplayer Beta Server Architecture Chris Hecker - SpyParty.com

  2. First, my demo…

  3. What the hell am I doing?

  4. Oh, by the way, you should ignore everything I’m about to say…

  5. Anyway, ignoring that elephant…

  6. “AAA Indie Games”

  7. “AAA Indie Games” Polished to Perfection Clearly Contain Lots of Love Highly Anticipated Before Launch

  8. My Goals For SpyParty’s Beta Infrastructure Polished Secure Scalable Flexible Are these the right goals?

  9. Polished (or, at least, able to be polished) Single-Sign-On Auto-discovery of Lobby Server(s) NAT Punchthrough, Relay Fallback, etc. Personalized Beta Homepage Ajax Forms, Private Forums, Bug Reporting & Feature Requests, etc.

  10. Secure No DIY Security! Single-Sign-On AuthN & AuthZ AuthN ClientServer & ClientClient https, TLS, revokable certs, timed downloads, etc. NB. this does not mean “unhackable” or “unwarezable”; certainly no DRM!

  11. Scalable Very Few Centralized Services Centralized Services Replicatable, Few Writes Run in the Cloud, Load Balanced Load Test Everything!!!Assume Nothing. Incremental Roll-out

  12. Flexible Where it sucks, know that I can fix it. Don’t be afraid to patch existing libraries.

  13. Some of the Components Amazon AWSS3, CF, EC2, SDB MIT Kerberos OpenLDAP PayPal IPN HMACOpenSSL UMich CoSign libjingle Perl, PHP, JS, C, bash, elisp, whatever! httpdvarnish

  14. Some questions… Why do all this yourself? Why not use Steam/XBLA/PSN/etc? Why not start with the “MVP” and iterate?

  15. Thank you! spyparty.com facebook.com/SpyParty twitter.com/SpyParty

More Related