The Skype Journey to 1ES and Cloud
summary
Migration from a peer-to-peer monolith to cloud microservices is described with concrete milestones: re-architecting client work into backend services, phased traffic rollouts, and progressive rollback rules. Built a shared one engineering system on VSTS and co-developed Maven/Ivy package support and Azure pipeline integrations. Scale and telemetry stats: roughly 1.8 million push notifications daily, 142 billion events daily, ~1,000 engineers across global sites. Result: microservices handle production scale, meet Office 365 compliance after mock audits, and enable DevOps ownership.
AI-written summary · about
chapters (11)
- 0:00Intro
- 7:00Building to High Availability
- 10:37Shift from Monolithic to Microservices
- 12:40Shift to DevOps
- 15:44Compliance and Security
- 18:32Big Data
- 21:32Skype
- 23:47Habits
- 25:37Engineers
- 26:18DevOps Assessment
- 27:08QA
related talks
15mTransitioning 69,000 engineers to one cloud system
33mMoving 75,000 Engineers To DevOps On The Public Cloud
07mWhat we learned moving 65,000 Microsofties to DevOps...
51mMicroservices and Microfrontends: Scaling, Learning, Growing
29mMoving from A and B to ~150 microservices, the journey and learnings
35mSeven years with microservices: a critical review
53mKeynote: Enterprise transformation (and you can too)
58mJourney to the Cloud - a Rearchitecting Story