Stage 7 · Master
Platform Engineering Fundamentals
Platform vs DevOps vs SRE
Clarify the distinctions and overlaps between platform engineering, DevOps culture, and Site Reliability Engineering.
7 min readPlatform Engineering & Developer ExperienceMaster
Core Definitions
| Discipline | Focus | Primary Metric | Team Type |
|---|---|---|---|
| DevOps | Culture & practices: collaboration, automation, measurement | Deployment frequency, lead time, MTTR | Cultural movement, not a team |
| SRE | Reliability of production systems via engineering | SLO adherence, error budget, toil reduction | Dedicated SRE team (Google model) or embedded |
| Platform Engineering | Internal developer platform as a product | DX metrics (scaffold-to-deploy, NPS), platform SLIs | Product team: PM, UX, Eng, Reliability |
The Venn Diagram
DevOps ∩ SRE ∩ Platform Engineering
Rendering diagram…
Responsibility Mapping
| Activity | DevOps (Culture) | SRE (Team) | Platform (Team) |
|---|---|---|---|
| CI/CD Pipeline | Teams own their pipelines | Reviews for reliability | Provides golden path pipeline template |
| Observability | Instrument your code | Defines SLIs/SLOs, builds tooling | Provides default dashboards, alerts, tracing |
| Incident Response | Team responds to their incidents | Leads major incidents, runs war room | Fixes platform bugs, provides runbooks |
| Capacity Planning | Team plans capacity | Models demand, sets quotas | Provides autoscaling, cluster capacity API |
| Security | Shift left, everyone's job | Defines security SLOs | Bakes policies into scaffold/admission |
| Developer Onboarding | Team mentors | N/A | Owns portal, scaffolder, docs, CLI |
How They Collaborate
- Platform builds the paved road; SRE defines the guardrails (SLOs, error budgets); DevOps is the culture that makes both work
- Platform team treats SRE as a key stakeholder — SRE requirements drive platform SLIs
- SRE uses platform APIs for automation (e.g.,
platform service scaleduring incident) - Platform team includes reliability engineers — platform reliability is a platform feature
- Enabling teams (security, data, ML) contribute capabilities to the platform, not point solutions
Organizational Patterns
| Pattern | Structure | When It Works | Risks |
|---|---|---|---|
| Platform Team Only | One platform team serves all stream-aligned teams | 5-50 developers, 3-10 services | Platform becomes bottleneck |
| Platform + Enabling Teams | Platform + Security Enabling + Data Enabling + ML Enabling | 50-500 developers | Coordination overhead |
| Platform per Domain | Platform team per business domain (payments, identity) | 500+ developers, distinct domains | Duplication, inconsistency |
| Federated Platform | Core platform team + domain platform engineers embedded in stream teams | 1000+ developers | Governance complexity |
Team Topologies Applied
Platform team = Platform (provides self-service APIs). Stream-aligned teams = Customers. Enabling teams = Security, Data, ML specialists who upskill stream teams and contribute to platform. Complicated subsystem teams = Rare, for truly unique tech (e.g., custom ML serving).
Mark this lesson complete to store local progress and unlock a cleaner resume path the next time you visit.