In Search of the Perfect Cloud Native Developer Experience
summary
Real consulting lessons: teams cut lead time by using telepresence and Squash proxies to develop locally against a remote Kubernetes cluster, adopt the Flux operator for GitOps to sync git to cluster, and roll features as a canary to 1% traffic before full release. Shopify-style work shows a successful Heroku-like wrapper over Kubernetes scales where Heroku cannot. Warnings include schema-migration canaries that broke 99% of traffic and the trade-off of building your own platform versus using cloud PaaS.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:16Delivering Value
- 4:23Developer Experience
- 8:25Workflows
- 9:54Progressive Delivery
- 11:52Microservice Patterns
- 16:45Should you build your own platform
- 17:55Netflix and Shopify
- 21:29Kubernetes
- 22:09Fundamental Questions
- 24:15Building a Platform
- 27:43Feedback
- 29:57Microservices
- 34:12Verification
- 39:56Dashboards
- 40:34Multiple Teams
- 40:57Where to Focus
- 44:53Summary
related talks
30mImproving the Cloud Development Experience: The Good, The Bad...
35mCloud Native Development Without the Toil
40mBeyond Productivity: Scaling Cloud Dev Environments for Faster Feedback & Sustaina...
39mCI/CD, APIs, and Scaling: What Every Cloud Native Developer Needs To Kn...
53mStreamline Cloud-Native App Development Using CDEs
26mClosing the Developer Experience Gap of K8s Development
24mFrom Kubernetes to PaaS to Developer Control Planes
29mHow to Get Your Application Developers to Fall in Love with Kubernetes & Cloud Native Applications