Platform, cost & AI
Platform engineering & Backstage
Many DevOps roles are now titled platform engineer, and senior interviews increasingly ask how you'd build an internal developer platform rather than how you'd write one pipeline. This topic explains what platform engineering is and why it emerged, how golden paths and self-service infrastructure work, how Backstage provides a catalogue, templates and docs, and how to run a platform as a product that developers actually choose to use, including how to measure it.
After this topic you can
- Explain platform engineering and golden paths
- Offer self-service infrastructure with guardrails
- Set up a Backstage catalogue and templates and measure a platform's success
Lessons
-
1What platform engineering is
- Why it emerged
- Team Topologies
- What a platform includes
-
2Golden paths and self-service
- Golden paths
- Self-service infrastructure
- Abstractions: how much to hide
-
3Backstage
- What Backstage is
- The catalogue
- Running Backstage
- Scorecards
-
4Building the platform as a product
- Platform as a product
- Measuring success
- Anti-patterns
-
5Interview questions and model answers
- "What is platform engineering, and how is it different from DevOps?"
- "How would you start building an internal developer platform?"
- "What's a golden path?"
- "What does Backstage give you, and what does it cost?"
- "How do you give developers self-service databases safely?"
- "How do you measure whether a platform is working?"
- "Teams refuse to adopt your platform. What do you do?"