Building a Cloud Native Culture in an Enterprise - Deep Kapadia & Tony Li
summary
The New York Times retires data centers and moves 300 apps to AWS and GCP, shutting down 140+ legacy services, using GKE for production and a Delivery Engineering team to create a GitHub-driven, self-service path from laptop to prod. Pipeline is Drone CI/CD building immutable binaries and Docker images, templating manifests, promoting via GitHub releases and Slack notifications; secrets delivered with Vault sidecars and 75 Vault namespaces supporting 21 teams. Fastly CDN logic is decentralized into ~40 repos; platform has processed ~50,000 jobs to date with 12,000 in the last month.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:19The NYT engineering enterprise
- 5:52And everything behind the scenes
- 7:49The initial foray into the cloud
- 9:32Starting a transformation
- 11:00What is "Delivery Engineering"?
- 12:12Using (more) modern tools
- 14:49Proof of concept
- 23:24Shifting processes (5)
- 25:33Shifting development (1)
- 26:22Shifting development (2)
- 27:40Shifting development (5)
- 30:22Shifting communication (1)
- 32:56Shifts in progress (3)
- 37:51Questions?
related talks
36mPractical Cloud Native: What Works, What Doesn't
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
25mFrom Heroku to Cloud Native in 7 Weeks
54mCloud Native Culture
42mCloud Native Applications
36mCultivating a Microservice Culture Via Tooling
01h 02mTransforming IT pros to DevOps gurus: Ssecure your new tech stacks
24mHow to survive Cloud – An Ops perspective