Lessons from the Trenches: Live Ops Game Data Architecture
summary
Panel covers concrete live Ops choices: mandate live Ops from day one, use 2 KB flag file feature toggles for emergency shutoffs, and expect Reddit to surface outages faster than internal tools by about two minutes. Recommend a three-person on-call rotation with primary/secondary/escalation and staged rollouts (Oceania first). Technical practices include server-side authority, hashed keys, struct shuffling and obfuscation, data validation and integration tests, Docker/VMs to avoid vendor lock-in, cheap leaderboard sharding, and a documented rollback plan after a 5 MB timeout region outage.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:13Planning live ops from day one
- 8:33Transitioning to live ops
- 12:33Preventing data leaks
- 17:26Stability for long-lived titles
- 22:00Server versus client logic
- 28:17Early server infrastructure
- 34:14Budgeting for live ops
- 38:46Anti-cheat and security
- 45:31On-call staffing challenges
- 45:51Automated testing pipelines
- 51:04Closing remarks
related talks
38mLive Ops Disaster Stories: What We Learnt
35mWhat is the 'gold standard' for live ops?
52mLet's Talk About LiveOps
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
38mCompany culture - Influencing live operations
21mManaging live operations game design
38mPanel: Interaction & Iteration: Best Practices for Getting the Most out of Your Live Ops Strategy.
25mChallenges of opportunities of operating live games