Platform API Deprecation
Removing something dozens of internal teams depend on, on a timeline that holds.
5 to work through
-
intermediate
A platform must deprecate an API or capability that many teams depend on. How is this done without destroying trust or stalling indefinitely?
2 min answer -
intermediate
A platform must remove a widely-used internal API. How should the deprecation be run?
2 min answer -
intermediate
An internal platform must remove a capability that several teams depend on. How should the deprecation be run?
2 min answer -
intermediate
You need to retire a platform API used by 60 services. Describe the plan.
2 min answer -
advanced
The platform is removing v1 of its config API. Telemetry showed 412 calling services at announcement; after six months of a funded migration 9 remain - 4 have no owner in the catalogue, 3 are monthly batch jobs that touch the API only on the first of the month, and 2 belong to a team that says it will not move this quarter. Removal was promised for the end of the quarter. Sequence the removal so you keep the date and stay reversible at every step.
3 min answer
3 terms in this topic
Deprecation Window
The stated period between announcing that an internal interface will be removed and removing it, with the removal actually happening at the end.
practicePlatform API Deprecation
Retiring a platform capability that other teams depend on, with the migration burden treated as the platform's problem rather than theirs.
practiceResidual Caller Tail
The handful of callers left at the end of a deprecation who will not move on their own, and the mechanisms that clear them so the removal date holds …
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.
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.