Successful Cloud Native Platform Engineering – Hype vs Reality
summary
Claims that only 40% of engineering time is productive and that 36% of engineers leave due to bad developer experience drive a platform built as a product: Backstage templates plus Git as the interface, automated repo creation and PRs, Argo for deployment, Captain + OpenTelemetry for automatic traces/metrics, OpenFeature for flags, Crossplane for infra, Jenkins/Harbor integration, and GitHub Codespaces for dev environments. Measured wins include Dell moving from ~35% to 83% productive time, 99% reduction in instrumentation effort, and up to 60% cost reduction by shutting unused VMs.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:23Developer productivity today
- 6:15What platform engineering is
- 9:05Demo setup and core components
- 13:42Real-world platform use cases
- 16:34Developer experience in large orgs
- 18:42Why platform observability matters
- 21:11Live demo results and feedback
- 22:57Key lessons learned
- 24:29Q&A
related talks
48mCombating the struggles of modern cloud-native java developers
29mImproving Developer Experience
25mFrom Ops to Impact: Scaling Engineering Velocity
31mPanel Discussion: Platform and Developer Productivity - Trends and Challenges
43mPlatform Engineering 101: Building Developer Platforms
27mTurning Platform Engineering Work Into Business Value Leadership Understands
54mDeveloper experience platforms
01h 07mCombating the struggles of modern cloud-native java developers