Skip to content
GitHub

Platform Engineering Discipline

Building internal products that make developers productive.

Overview

Section titled “Overview”

Platform Engineering is the discipline of designing and building toolchains and workflows that enable self-service capabilities for software engineering organizations. Unlike traditional infrastructure teams that respond to tickets, platform teams build products that enable developers to do their own infrastructure work safely and efficiently.

Learning Objectives

Section titled “Learning Objectives”

After completing this track, you will be able to:

  • Explain what platform engineering is and how it differs from DevOps
  • Apply the platform-as-a-product mindset to internal tooling
  • Design for developer experience using cognitive load theory
  • Architect Internal Developer Platforms (IDPs)
  • Create effective golden paths that developers actually want to use
  • Implement self-service infrastructure with appropriate guardrails
  • Assess platform maturity and build improvement roadmaps

Prerequisites

Section titled “Prerequisites”

Before starting this track, you should:

  • Understand Kubernetes fundamentals (deployments, services, namespaces)
  • Be familiar with CI/CD concepts and tools
  • Have experience with infrastructure-as-code (or complete IaC Discipline)
  • Complete the Systems Thinking foundation track (recommended)

Modules

Section titled “Modules”
#ModuleComplexityTimeDescription
2.1What is Platform Engineering?MEDIUM35-45 minOrigins, platform-as-a-product, Team Topologies
2.2Developer ExperienceMEDIUM40-50 minSPACE framework, cognitive load, flow state
2.3Internal Developer PlatformsCOMPLEX50-60 minFive pillars, reference architectures, build vs buy
2.4Golden PathsMEDIUM40-50 minDesign, mandates vs paths, maintenance
2.5Self-Service InfrastructureCOMPLEX50-60 minAbstractions, guardrails, lifecycle management
2.6Platform MaturityMEDIUM45-55 minAssessment, dimensions, roadmaps

Total Time: ~4.5-5.5 hours

Learning Path

Section titled “Learning Path”
Module 2.1: What is Platform Engineering?
    │
    ├── Understand the origin and evolution
    ├── Learn platform-as-a-product mindset
    └── Apply Team Topologies patterns
          │
          ▼
Module 2.2: Developer Experience
    │
    ├── Measure with SPACE framework
    ├── Reduce cognitive load
    └── Enable flow state
          │
          ▼
Module 2.3: Internal Developer Platforms
    │
    ├── Understand the five pillars
    ├── Choose reference architecture
    └── Make build vs buy decisions
          │
          ▼
Module 2.4: Golden Paths
    │
    ├── Design effective paths
    ├── Balance guidance with autonomy
    └── Maintain over time
          │
          ▼
Module 2.5: Self-Service Infrastructure
    │
    ├── Create useful abstractions
    ├── Implement guardrails
    └── Manage full lifecycle
          │
          ▼
Module 2.6: Platform Maturity
    │
    ├── Assess current state
    ├── Identify gaps
    └── Build improvement roadmap

Key Concepts

Section titled “Key Concepts”

Platform Engineering vs DevOps

Section titled “Platform Engineering vs DevOps”
AspectDevOpsPlatform Engineering
FocusProcess and cultureProducts and tooling
ModelEmbedded in teamsSeparate team serving teams
Success metricDeployment frequencyDeveloper productivity
InteractionCollaborationSelf-service

The Platform-as-a-Product Mindset

Section titled “The Platform-as-a-Product Mindset”

Platform teams treat developers as customers:

  • Research needs before building
  • Measure adoption and satisfaction
  • Iterate based on feedback
  • Compete with alternatives (shadow IT)

The Five IDP Pillars

Section titled “The Five IDP Pillars”
┌─────────────────────────────────────────────────────────────────┐
│                   INTERNAL DEVELOPER PLATFORM                    │
├─────────────────────────────────────────────────────────────────┤
│                                                                  │
│  ┌──────────┐  ┌──────────┐  ┌──────────┐  ┌──────────┐       │
│  │Developer │  │ Infra    │  │  App     │  │ Security │       │
│  │ Portal   │  │Orchestr. │  │ Delivery │  │& Govern. │       │
│  └──────────┘  └──────────┘  └──────────┘  └──────────┘       │
│                                                                  │
│                       ┌──────────┐                              │
│                       │Observa-  │                              │
│                       │bility    │                              │
│                       └──────────┘                              │
│                                                                  │
└─────────────────────────────────────────────────────────────────┘

Cognitive Load Types

Section titled “Cognitive Load Types”
TypeDescriptionPlatform Strategy
IntrinsicComplexity inherent to the taskCan’t eliminate, can support
ExtraneousUnnecessary complexityEliminate through platform
GermaneLearning that builds expertisePreserve and enable
Section titled “Related Tracks”

Foundations (Start here if new to these concepts):

Disciplines (Apply platform engineering in context):

Toolkits (Deep dive into specific tools):

Tools You’ll Encounter

Section titled “Tools You’ll Encounter”
ToolPurpose
BackstageDeveloper portal, service catalog
CrossplaneInfrastructure orchestration
ArgoCD/FluxGitOps delivery
OPA/GatekeeperPolicy as code
Kustomize/HelmConfiguration management
OpenTelemetryObservability

Progress Checklist

Section titled “Progress Checklist”
  • Module 2.1: What is Platform Engineering? - Foundations
  • Module 2.2: Developer Experience - Measurement and improvement
  • Module 2.3: Internal Developer Platforms - Architecture
  • Module 2.4: Golden Paths - Template design
  • Module 2.5: Self-Service Infrastructure - Provisioning patterns
  • Module 2.6: Platform Maturity - Assessment and roadmaps

Quick Reference

Section titled “Quick Reference”

Platform Team Anti-Patterns

Section titled “Platform Team Anti-Patterns”
Anti-PatternDescriptionFix
Build it and they will comeNo adoption focusTreat platform as product
Golden handcuffsMandates, not pathsMake the right thing easy
Ticket queueStill ticket-basedBuild self-service
Perfect platformNever shipMVP + iterate

Maturity Levels

Section titled “Maturity Levels”
LevelNameCharacteristics
1ProvisionalAd-hoc, tribal knowledge
2OperationalBasic automation, some self-service
3ScalableSelf-service works, metrics tracked
4ManagedBusiness impact measured, proactive
5OptimizingContinuous improvement, industry leader

Success Metrics

Section titled “Success Metrics”
Adoption:
  - Golden path usage rate
  - Self-service success rate
  - Time to first deploy


Satisfaction:
  - Developer NPS
  - Support ticket volume
  - Cognitive load surveys


Impact:
  - Deployment frequency
  - Lead time for changes
  - Platform ROI

Further Reading

Section titled “Further Reading”

Books

Section titled “Books”
  • Team Topologies - Matthew Skelton & Manuel Pais
  • The Phoenix Project - Gene Kim, Kevin Behr, George Spafford
  • Accelerate - Nicole Forsgren, Jez Humble, Gene Kim

Articles

Section titled “Articles”

Conferences

Section titled “Conferences”