Cloud Native Developer Experience in 2025
summary
Demo stack shows concrete wins and tradeoffs: dev containers + Podman and VS Code automates per-project envs but hits container filesystem and networking limits; Flux/Nix produces reproducible, multi‑arch host-based dev environments via a declarative manifest; Go build with ko creates multi‑arch images without Dockerfiles and rejects uncommitted changes; Java uses Buildpacks/pack (and gradle bootBuildImage) to auto-detect stacks. Live demo of scaffold syncs changed files into a Kubernetes pod and serves updated responses, proving inner‑loop iteration works end-to-end.
AI-written summary · about
chapters (9)
- 0:00Introduction and motivation
- 8:31Development environments and friction points
- 13:24Dev containers and activation patterns
- 28:10NixOS and Flux for environments
- 35:08Kubernetes and containerization
- 37:15Source to image patterns
- 41:07Build packs for Java and Go
- 45:19Live reload with Scaffold
- 50:55Book overview and future trends
related talks
44mCloud Native Applications with Remote Development Environments
53mStreamline Cloud-Native App Development Using CDEs
35mCloud Native Development Without the Toil
30mClosing the Developer Experience Gap of your Container Platforms
32mCloud Native Progressive Delivery
07mKeynote: Container-Native Dev-and-ops Experience: It's Getting Easier, Fast.
50mCloud-Native Dev Tools: Bringing the cloud back to earth
20mWhat Does A Platform On Kubernetes Look Like?