Local Microservice Development: Remote Kubernetes Assist
summary
A concrete engineering journey: started with per-repo Docker Compose overlays to run dependency services locally, moved those merged configs through Kompose into a remote Kubernetes namespace with port‑forwards, and finally replaced fragile shell scripts with a Kotlin CLI (biodome/devcube) and Gradle plugins. Result: laptops cool down, heap and CPU pressure drop, local dev still debugs against real deps, system runs in production for years, snapshots and auto‑provisioning work, onboarding friction shrinks.
AI-written summary · about
chapters (21)
- 0:00Local microservice development
- 1:28Talk overview
- 3:13StackHawk platform architecture
- 5:01AWS build platform setup
- 7:51Developer workflow challenges
- 8:32Docker Compose dependencies
- 10:41Docker Compose in practice
- 13:33Docker Compose performance issues
- 14:16Compose with k and devcube v1
- 16:04Devcube v1 and Kubernetes
- 17:48Shell script tool limitations
- 19:16Gradle build tool
- 21:04Transition to Kotlin tools
- 23:11Devcube v2 with Kotlin
- 24:14Configuration language
- 25:41Devcube commands
- 27:45Gradle devcube integration
- 28:28Internal developer platform
- 29:12Future biodome enhancements
- 31:58Developer platform benefits
- 32:39Acknowledgments
related talks
32mLocal development techniques with Kubernetes
42mLocal Development Techniques with Kubernetes
31mJKube Remote-Dev: Code with All Your Cloud Microservices... Locally!
49mDeveloping microservices applications on the Kubernetes platform
45mBuilding a Kubernetes Integrated Local Development Environment
38mDeveloping Locally with Kubernetes
22mMaking Kubernetes How We Build Things
45mKubernetes Local Development Workflow Distilled