Platform Team Topologies
Stream-aligned, enabling, complicated-subsystem and platform teams, and their interactions.
3 to work through
-
beginner Multiple choice
Six platform engineers support forty product teams. Each team raises roughly 1.5 requests a week and each request costs about 90 minutes of an engineer's time once the context switch is counted. Roughly how much of the team's capacity is interrupt work and what does that number rule in or out?
2 min answer -
advanced
A team of six owns nineteen services and is missing every deadline. They ask for more engineers. Is that the right answer?
2 min answer -
advanced
How should platform work be organised as an organisation grows, and what structure prevents the platform becoming a bottleneck?
2 min answer
3 terms in this topic
Cognitive Load
The total amount a team must hold in mind to do its work, treated as a hard constraint on how much a team can own.
patternEnabling Team
A team whose output is other teams' increased capability, working alongside them temporarily rather than owning a component permanently.
case-studyThe Spotify Model and Why Its Authors Warned Against Copying It
An influential description of Spotify's team structure was widely adopted as a template, and people who were there have since cautioned that it was a…
Neighbouring topics
Platform Engineering
General material on internal platforms as products with users, adoption and lifecycles.
Internal Developer Platform
The assembled surface teams actually touch, and what belongs behind it.
Paved Road & Golden Path
A supported default route that is easier than the alternatives rather than mandatory.
Self-Service Provisioning
Teams getting infrastructure without a ticket, and the guardrails that make that safe.
Service Templates
Scaffolding new services with observability, CI and security already wired in.
Platform APIs
Treating the platform's own interfaces as contracts with consumers and compatibility rules.
Platform Tenancy
Isolating teams sharing a cluster, account or pipeline fleet, and where isolation must be hard.
Cluster Architecture
How many clusters, split by what, and the blast radius each split buys.
Service Mesh Operations
What a mesh genuinely solves, its failure modes, and the cost of running one.
Container Image Strategy
Base images, layer hygiene, rebuild cadence, and patching a fleet of images.
Developer Environments
Local, remote and ephemeral environments, and the fidelity each can honestly claim.
Inner Loop & Outer Loop
Where an engineer's time actually goes, and which loop a platform investment shortens.
Abstraction Level Choice
How much to hide, and the leak that turns a helpful abstraction into a trap.
Platform SLOs
Committing to reliability for internal consumers who cannot choose another provider.
Platform Adoption
Migrating existing teams onto a platform without a mandate, and reading the adoption curve.
Platform Funding
Central cost, showback, chargeback, and justifying a team that ships no customer feature.
Platform API Deprecation
Removing something dozens of internal teams depend on, on a timeline that holds.
Guardrails vs Gates
Preventing a class of mistake automatically versus stopping to ask a human.
Platform Telemetry
Instrumenting the platform itself: usage, friction, and where teams leave the paved road.