Combating the struggles of modern cloud-native java developers
summary
Claims measurable wins: an internal developer platform plus portal cuts environment wait time ~90%, boosts deployment frequency ~4x, and shortens lead time; platform teams report ~95% fewer config files and orgs see ~30% faster time-to-market with ~80% lower TCO. Implementation is a stitched toolchain—examples include Backstage, Argo CD and Crossplane with IaC like Terraform—delivering golden path self-service. Expect upfront build and ongoing maintenance costs and possible platform-team resource strain.
AI-written summary · about
chapters (16)
- 0:00Introduction and welcome
- 1:04Why cloud-native Java struggles
- 3:11Shift left and cognitive load
- 8:04Container management challenges
- 10:52Developer burnout and struggles
- 13:38Platform engineering introduction
- 17:06DevOps vs platform engineering
- 21:20Internal developer platforms
- 25:14Internal developer portals
- 26:39Benefits of platform engineering
- 32:21Challenges of platform engineering
- 35:29IDP reference architectures
- 36:11Backstage and developer portals
- 41:10Choosing IDP tools
- 42:58Future of platform engineering
- 45:47Summary and closing
related talks
01h 07mCombating the struggles of modern cloud-native java developers
48mCombating the Struggles of Modern Cloud Native Java Developers
29mSuccessful Cloud Native Platform Engineering – Hype vs Reality
20mPlatform-First Cloud Transformation
24mA Cloud Native Foundation For Developer/Application Platforms
11mBuilding Scalable Developer Platforms
36mCloud-Native Dev Tools: Bringing the cloud back to earth
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines