Self-service for delivery value with platform engineering
summary
Paper describes a platform engineering effort that replaces 100‑field ticket workflows with an internal developer platform composed of four concrete components: a database self-service portal (CLI/API/portal) that provisions AWS/GCP instances on demand, a logging library standard to unify logs, a policy interceptor that enforces CPU/memory and image verification on Kubernetes, and a plug‑and‑play observability pipeline. Outcomes: faster provisioning, fewer duplicate requests, tighter resource governance and measurable cost efficiency across multiple teams.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 7:23Traditional way problems
- 13:11Self-service concept
- 21:10Platform engineering explained
- 27:59Case study one logging
- 31:59Case study three abstraction
- 36:57Case study four observability
- 38:43Summary and Q&A
related talks
29mThe Platform Engineering Revolution Panel: Empowering Developers Through Self-Service
39mPlatform Engineering as a (Community) Service
44mPlatform Engineering in action
33mPlatform engineering: Build your own PaaS
15mThe Art of Platform Engineering
41mPlatform Engineering for Developers, Architects & the Rest of Us
42mPlatform Engineering in practice — Why and How to start
28mWhat's Next in Platform Engineering