Driving Sustainability with Delivery Engineering
summary
Argues Delivery Engineering drives organizational sustainability by applying three DevOps-informed practices—culture, automation, measurement—and shows concrete artifacts: standardized runtime templates and optional frameworks, reusable runtime packages, Helm-based config templates, a developer portal (Backstage-style) integrated with GitHub and an artifact manager, and OpenTelemetry for telemetry. Describes CI/CD with Drone, automated Helm chart generation, and metrics-triggered automatic rollbacks. Notes trade-offs: frameworks reduce drift but created tech debt in one org, vendor lock‑in risks, and the need for a clear build vs buy decision framework.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 7:50Community Learning
- 15:15Support Strategies
- 19:54Platform Architecture
- 23:20Design Tensions
- 26:21Platform Recipe
- 30:53Runtime Templates
- 32:00Runtime Frameworks
- 34:54Packages
- 38:04Infrastructure Management
- 40:39Production Readiness
- 43:11Telemetry Collection
- 46:24Putting it all together
related talks
29mDriving organizational sustainability with Platform Engineering
41mOrganizational Sustainability with Platform Engineering
46mOrganizational Sustainability with Platform Engineering
24mWhy, What, and How of Continuous Delivery
37mDevOps, 12 Factor and Platform Engineering
59mNow That My Delivery Pipeline Is in Place, What About My Organization?
31mBridging Product and Engineering for a Greener Future: Embedding Sustainability into Software Teams
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform