Platform Engineering 101: Building Internal Developer Platforms
summary
Argues that building an Internal Developer Platform cuts developer cognitive load by providing OpenShift and Red Hat Developer Hub as a managed stack, a Backstage-based portal for a single-pane view, and baked golden paths for CI/CD. Demo bootstraps an Open Liberty template, creates two GitLab repos, runs a pipeline that builds and signs images, produces an SBOM and scans for vulnerabilities, and triggers Argo CD deploys to dev/pre-prod/prod; pipeline takes minutes and the end-to-end flow completes (demo shows transient build delay).
AI-written summary · about
chapters (22)
- 0:00Introduction
- 2:05Developer struggles in cloud
- 3:31Shift left and cognitive load
- 8:44Developer burnout causes
- 10:09What is platform engineering
- 13:45Internal platforms vs portals
- 15:50Benefits of platform engineering
- 17:57Challenges in platform engineering
- 18:39Tools for platform engineering
- 20:45Demo setup
- 21:50Software templates and golden paths
- 25:49Bootstrapping new project
- 27:14Dev Spaces and developer experience
- 29:23Components catalog and CI pipelines
- 31:11Security scanning and image signing
- 32:12Argo CD and deployment monitoring
- 33:39Benefits of single pane of glass
- 34:21APIs and documentation
- 35:42Automation workflows and self-service
- 36:50Alternative tools
- 37:31Summary and future
- 40:23Q&A
related talks
42mPlatform Engineering 101: Building Internal Developer Platforms
43mPlatform Engineering 101: Building Developer Platforms
43m#PlatformEngineering 101 Building #InternalDeveloperPlatforms
34mEmpower Developer Experience
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
54mDeveloper experience platforms
11mBuilding Scalable Developer Platforms
44mPlatform Engineering in action