Is Platform Engineering a hype? Let's build a platform together!
summary
Claims that a usable internal platform can be built quickly and incrementally and demonstrates one built end-to-end: a four-person family team builds an MVP platform on a laptop using kind for local Kubernetes, Cluster API to provision clusters, GitHub Actions + GHCR for CI/CD, Helm charts and Flux/Flagger for GitOps and progressive delivery, Crossplane for RDS provisioning, Teleport for SSO, and Prometheus/Grafana for monitoring. The neighbor’s Node.js app deploys via the GitOps flow, proving the approach works.
AI-written summary · about
chapters (5)
- 0:00Introduction to platform engineering
- 10:03Defining a platform mindset
- 20:22Building the platform MVP
- 33:37Adding observability and security
- 40:43Key takeaways and next steps
related talks
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
14mOvercoming Kubernetes Complexity with Platform Engineering
45mPlatform Engineering vs DevOps
18mThe Past, the Present, and the Future of Platform Engineering
26mTwo sides of the platform coin with operator's and customer's voices
52mFrom Silos to DevOps to Platform Engineering: embracing GitOps and going behind the hype
33mWhy You Should Treat Your Platform as a Product
36mHow to Build Cloud-Native Platforms with Kubernetes