What to Expect from Your Application Platform
summary
Introduce a product manager to prioritize platform work; treat the platform as a maintained product, not a one‑off. Platform must enforce shift left without shifting burden by generating SBOMs, enabling developer triage of CVEs (don’t just block with an admission controller), and encoding runtime services and opinions (Kubernetes, regional HA, Spring Boot portability). Provide paved paths or micro‑platforms with templated YAML, a developer portal that triages and deep‑links (Backstage + dashboards that link out to Datadog), and CI/CD integration.
AI-written summary · about
chapters (10)
- 0:00Introduction and backgrounds
- 3:10Shift from central IT to platforms
- 4:56DevOps to platform engineering
- 6:21Platform as a product
- 9:11Shift outcomes left without burden
- 14:29Collaboration in platform design
- 15:11Paved paths for consistency
- 20:28Encoding runtime services
- 24:20Developer portal benefits
- 28:10Q&A and closing
related talks
41mPlatform as a Product
39mPlatform Engineering as a (Community) Service
41mPlatform Engineering for Developers, Architects & the Rest of Us
33mPlatform as a Product - Transforming from Service Delivery into Continuous Operations
32mHow we did Platform Engineering at Datadog
13mBuilding Platforms Through Customer Value: Yes, You Can
39mThe challenges of Platform teams (and few tips & tricks...)
42mPlatform Engineering in practice — Why and How to start