Platform Capabilities Layers
You'll learn how modern internal developer platforms organize functionality into distinct architectural layers that work together to deliver self-service infrastructure.
Understanding the Stack
Think of a platform like a building: it needs a foundation, plumbing, delivery systems, and monitoring throughout. A well-designed Internal Developer Platform (IDP) organizes capabilities into four core layers that stack vertically:
1. Infrastructure Layer
The foundation. This is where compute, storage, networking, and cloud resources live. It's the raw materials—VMs, Kubernetes clusters, databases, load balancers. Without this, nothing else works.
2. Provisioning Layer
The automation engine. This layer handles how infrastructure gets created, configured, and managed. Terraform modules, CloudFormation templates, and configuration management belong here. It translates developer requests ("I need a database") into actual resources.
3. Delivery Layer
The golden paths. This is where CI/CD pipelines, deployment workflows, artifact registries, and release management live. It moves code from commit to production safely and repeatably. It's what developers interact with most directly.
4. Observability Layer
The nervous system. Logging, monitoring, tracing, and alerting span all other layers. This provides visibility into what's happening across the entire platform, enabling teams to understand behavior, troubleshoot issues, and ensure reliability.
Why Layers Matter
Separating concerns into layers makes platforms maintainable and composable. Teams can improve one layer without disrupting others. You can swap monitoring tools without touching provisioning logic, or update deployment patterns without changing infrastructure.
Key Takeaway: Platform capabilities organize into four fundamental layers—infrastructure, provisioning, delivery, and observability—each with distinct responsibilities that together enable developer self-service on paved roads.