Building for Scale: How not to get Caught out at Global Launch
summary
Argues that planning for scale up front is ~100x cheaper than firefighting later and that common soft‑launch shortcuts break under millions of players — e.g. large JSON configs cause crashes on old phones and databases become the first bottleneck. Recommends three concrete moves: spec now, implement later, invest in over-the-air update pipelines (designer spreadsheets → optimizer/validator → release management → archived binary configs) and design modular, swappable services. Metaplay built that pipeline, it prevents rollbacks and speeds economy tuning, and the company publishes the tech and source for reuse.
AI-written summary · about
chapters (11)
- 0:00Scaling game launches
- 1:47Time to market matters
- 3:10Hidden cost of hyperfocused teams
- 4:55Four scaling factors after launch
- 6:44Game complexity post-launch
- 9:38Hope is not a strategy
- 10:21Three actions for scale
- 12:07Hardcoded config pitfalls
- 14:17OTA update system design
- 16:46Victory with planning
- 17:27Key takeaways
related talks
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
44mLive Ops Strategies That are a Must for Every Game Developer
37mBuilding Apps that Scale
41mReinventing Game Launches: A Framework for Success
27mScaling Your Front-End in a Realistic Way!
25mBuild Failed Startups—Not Side Projects
19mScaling Fast – Engineering Lessons From ~15 Years of Tech Startups
15mBuilding SRE Culture (without SREs, Technically)