Platform Engineering vs DevOps
summary
Argues that platform engineering delivers DevOps by building a developer-focused platform with self-service templates and automation rather than pushing infrastructure knowledge onto devs. Describes a minimal internal developer platform (Svelte front end, .NET API) that creates repos, injects GitHub Actions workflows and Bicep IaC, registers an Entra app and uses OIDC federated credentials to avoid long-lived secrets. Recommends Azure tools: Bicep/Terraform, Container Apps, Key Vault, Container Registry, Grafana/Prometheus, and splits ops into platform engineer, SRE and cloud engineer roles; demos mostly work but one registration step fails live.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:29What is DevOps
- 4:39Defining platform engineering
- 6:25DevOps vs platform engineering
- 8:57Organizational maturity stages
- 11:42Platform engineering in practice
- 15:12Platform engineering iceberg
- 23:25Demo: minimal internal dev platform
- 30:00Goals of platform engineering
- 33:53Recap and key takeaways
- 35:18Q&A
related talks
41mPlatform Engineering for Developers, Architects & the Rest of Us
15mThe Art of Platform Engineering
39mPlatform Engineering as a (Community) Service
22mDevOps vs Platform Engineering: Navigating the Path Ahead
33mPlatform engineering: Build your own PaaS
45mDevOps Is Dead, Long Live Platform Engineering!
25mPlatform Engineering: Evolution or a Fancy Rename?
21mMake developers fly; Principles for platform engineering