Moving From A Monolith To An API Economy At Columbia
summary
Columbia moves to a public-cloud-first Azure model and builds an open data platform of microservices and APIs, using Service Bus, Event Hub, Azure Functions, API Management, Azure Data Factory, HDInsight and Azure Data Warehouse. The program starts with a 250-artifact version control goal and exceeds 500, reverse-engineers and automates over 1,500+ servers, standardizes deployments with YAML build definitions and ARM template abstractions, implements CI/CD (artifact repo, SpecFlow tests, SonarQube) and proves value with a SOX pipeline and a near‑real‑time package‑tracking API.
AI-written summary · about
chapters (16)
- 0:00Introduction and background
- 1:05Monolith challenges and crisis
- 2:50Starting with version control
- 4:33Becoming a learning organization
- 6:39ChatOps and team transformations
- 8:26Moving to product organization
- 10:13Automating continuous delivery
- 13:25Tim's role and business shifts
- 14:29Data as the new oil
- 15:31Modernizing data landscape
- 17:38Dumping the rind keeping juice
- 20:05Bringing others along
- 21:31Starting with SOX compliance
- 22:56Equipping teams for success
- 24:20Defining clear outcomes
- 26:05Perfect conditions for change
related talks
30mEnabling Public Cloud For Clients in a Public Sector
35mRoad to Efficient and Data-Driven DevOps
15mTransitioning 69,000 engineers to one cloud system
29mTaming the Hybrid Beast with DevOps
26mTransition to the Cloud Return
28mScale Your DevOps Initiative Beyond Its Awkward Teenage Years
55mBuild your Cloud Operating Model on Azure from zero to hero
25mChanging the Development Culture at Comcast and Our Evolution from Legacy SOA to Cloud Native