A Cloud Native Foundation For Developer/Application Platforms
summary
Argues platform engineering must deliver a cloud‑agnostic foundation that actually provisions infra and developer workflows: uses crossplane plus Backstage, Argo and buildpacks as a plug‑and‑play stack, treats the container registry and Git as a container registry as security breakpoint for scanning and SBOMs, splits CI from CD for fast local feedback, and measures success by low script counts, few interdependent components and simple docs. Notes Azure support gaps, containers not fully isolating, and enterprises average 2.4 public cloud providers.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:40INTRODUCTION
- 1:51What we are talking about
- 3:40Platform or Internal Dev Platform
- 4:34Orchestrate Chaos
- 5:39The ideal IDP
- 8:27What you want to achieve
- 9:01Or even better
- 9:43Lessons Learned - the little things
- 11:45Complexity of Platforms
- 12:33Kubernetes is not a hypervisor
- 14:14The cloud provider matter
- 16:16CI/CD a mythos/dilemma
- 19:21You need a unified observability
- 20:00Deliver to Devs the full view
- 20:35What doesn't work well, yet
- 22:43Some key metrics building a platform Bert bay
related talks
11mKeynote: Steampunk Meets Cyberpunk: The Makings of a Cloud Native Application Platform
29mYour platform is not an island: building a platform for your ecosystem
12mUnveiling the Future: Navigating Cloud Strategy, Platform Engineering, and Architectural Evolution
45mPlatform Engineering vs DevOps
48mCombating the struggles of modern cloud-native java developers
35mCloud Native Development Without the Toil
15mPaaS isn’t enough: your internal platform in Multi Cloud
23mHow the Cloud Foundry Community Can Help Platform Engineering