Improving the Cloud Development Experience: The Good, The Bad...
summary
Argues that using Kubernetes + Crossplane makes development environments identical to production and self-service, not ad hoc local hacks. Shows a Taco Shop app where Crossplane provisions SQS and S3 resources and Helm/Octeto deploys microservices into per-developer namespaces with live code sync and a shareable URL. Demonstrates a single-command self-service flow, cites deployments of 10–100 microservices, and explains cost/scale tradeoffs and options for full, partial, or shared remote environments.
AI-written summary · about
chapters (9)
- 0:00Introduction to dev experience
- 1:20Defining roles and personas
- 4:43Challenges in modern development
- 7:37Identifying bad experiences
- 11:48Progress in cloud development
- 13:57The kubernetes way
- 17:18Infrastructure with Crossplane
- 21:05Demo: Self-service deployment
- 26:13Q&A and closing thoughts
related talks
33mEliminating the Gap Between Development and Production with Kuber...
46mIn Search of the Perfect Cloud Native Developer Experience
24mFrom Kubernetes to PaaS to Developer Control Planes
53mStreamline Cloud-Native App Development Using CDEs
44mCloud Native Applications with Remote Development Environments
17mCrossplane: Deploy Your Cloud Components from Your K8S Cluster
33mLevel Up Your Developer Experience 🧭
33mUnifying Developer Experience Across Virtual and Cloud Native Worlds