The Past, the Present, and the Future of Platform Engineering
Talkat Platform Engineering Day 2025 - Europe · on Tuesday, 2025-04-01· at 10:40· Level 1 | Hall Entrance N10 | Room H·
summary
Platform engineering is framed as decades of repeated failure then a clear pattern emerges: API + controllers pattern layered on Kubernetes as the standard base, not a container toy. Practical tools named: Jenkins, Docker, Argo CD, Crossplane, KNative, Backstage and blueprints like Backstage+Crossplane+Kerno+Argo CD that assemble them. Emerging projects for multicluster and AI are KCP, Q, Carport and Dapper, and the hard truth is platforms must expose domain APIs, add governance, observability and resilience, and then decide whether to hide Kubernetes from developers.
AI-written summary · about
chapters (15)
- 0:00Developer to platform builder
- 3:15Early platforms: application servers
- 5:02CI tools like Jenkins
- 6:48Docker and container revolution
- 7:32Kubernetes and industry-wide agreement
- 9:18Platform engineering history
- 10:00Pattern behind platforms
- 12:30Kubernetes controllers
- 14:37Domain-specific platforms
- 16:23Hiding Kubernetes complexity from developers
- 18:05Platform blueprints today
- 20:13Future of platform engineering
- 22:18Multicluster management tools
- 23:42AI in platforms securely
- 25:27Q&A
related talks
32mPlatform Engineering for Software Developers and Architects (Redux)
48mPlatform Engineering is Domain Driven Design
47mPlatform Engineering is Domain-Driven Design
01mPlatform Engineering is Domain Driven Design
51mThe Magic of Platforms
58mPlatforms: Build abstractions, not illusions
22mBuilding a Platform Framework: Lessons Learned From Developing a Multi-Cluster Kubernetes Operator
29mLeading With The Platform: A Platform Engineering Approach To Tech Debt