Platform Engineering beyond the Buzzword?
summary
Argues that platform teams must reduce developer cognitive load rather than become another bottleneck, and recommends shifting ownership to product teams via a developer API and custom resource declarations in GitLab. Demonstrates spinning per-team Kubernetes with Argo operators, offering Kafka either via Strimzi in-cluster or managed MSK, and automating topic creation with operators. Warns monolithic platforms create a single-point-of-failure while fully decentralized platforms add operational complexity, so the path is a staged move toward team-owned platforms.
AI-written summary · about
chapters (10)
- 0:00Platform engineering intro
- 1:04Why platform engineering exists
- 3:11Horizontal to vertical teams
- 5:59Golden path paradox
- 8:24Platform teams reduce load
- 10:07Monolithic platform pitfalls
- 12:37Distributed platform challenges
- 14:43Platform as product dev
- 16:10Self-service dev API
- 17:33Simplicity vs scalability
related talks
32mPlatform Engineering Is Not About Tech
46mBeyond DevOps: How and Why Companies Converge on Platform Models
30mPlatform as a Product
40mPlatform Wars: The Battle Between Golden Paths and Spaghetti Pipelines
33mThe Platform Engineering Journey
32mThe Past, the Present, and the Future of Platform Engineering
44mPlatform Engineering is All About Product
37mPlatform Engineering's Inferno