Abstraction Level Choice
How much to hide, and the leak that turns a helpful abstraction into a trap.
4 to work through
-
advanced
A platform must choose how much of the underlying infrastructure to abstract. What decides the level?
2 min answer -
advanced
A platform team must decide how much to abstract the underlying infrastructure. What goes wrong at each extreme, and how do you choose?
2 min answer -
advanced
An internal platform must decide how much of the underlying infrastructure to hide. What determines the right abstraction level, and what happens at each extreme?
2 min answer -
advanced
Your platform abstracts Kubernetes entirely — teams write a short manifest and everything is generated. Now every production incident escalates to the platform team. What is happening?
2 min answer
5 terms in this topic
Escape Hatch
A supported way for a team to bypass part of a platform abstraction and work with the underlying primitives - which is what makes an abstraction safe…
practiceEscape Hatch
A supported route from a platform's simple default down to the underlying primitives - so a team with an unusual need adapts within the platform rath…
patternGraduated Escape Hatch
The ability to override one component of a platform's abstraction without abandoning the rest - which prevents a single unmet requirement from causin…
conceptLeaky Abstraction Cost
What a consumer pays when a platform abstraction hides a mechanism they must nonetheless understand to diagnose or tune it.
conceptPlatform Abstraction Level
How far a platform hides the underlying infrastructure, and the leak-versus-flexibility trade it makes at that height.
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.
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.
Platform Team Topologies
Stream-aligned, enabling, complicated-subsystem and platform teams, and their interactions.