How to run a global, cloud scale event for 10.000 people
summary
Claim: a global event spans 10,000 participants across 35 countries, provisions 1,400 websites and databases, triggers Azure DevOps outages and still costs half the expected budget. Automation uses Azure pipelines, Selenium-based console tooling, AKS and App Services instead of ACI, and Docker containers to run ~30,000 challenge instances. Soft regional limits and SQL service quotas force workarounds, observability and backloged role assignments create incidents, and the platform runs for 36 continuous hours with manual fallbacks.
AI-written summary · about
chapters (6)
- 0:00Start
- 8:42STAKEHOLDER MANAGEMENT
- 9:0090 venues worldwide
- 24:21COST MANAGEMENT
- 39:40RISK MANAGEMENT
- 40:47CUSTOMER HAPPINESS
related talks
20mManage Scaling, While Keeping Costs Under Control. Challenge Accepted.
01h 01mEmbrace chaos to achieve stability
59mRunning a real world, mission-critical system on Azure
37mA startup's infrastructure - how to make scaling a sales, not a tech issue
46mManaging a Billion Transactions with Tech, Tactics, and Teamwork
53mImmutable Infrastructure on Azure
46mReal World DevOps
48mDevops@Scale