Service Templates
Scaffolding new services with observability, CI and security already wired in.
4 to work through
-
intermediate
A platform provides service templates and teams' services diverge from them within months. What should the template strategy be?
2 min answer -
advanced
A platform stops generating 400 lines of observability and deployment boilerplate into each new service repository and ships it instead as a versioned library plus a shared base chart that services depend on. Two hundred services will adopt it. What is gained and what is paid and when does the bill arrive?
3 min answer -
advanced
A platform's service template produced fifty services, and it has since improved substantially. How should improvements reach the existing services?
2 min answer -
advanced
A vulnerability is found in the base image used by 200 services generated from your service template. How do they all get fixed?
2 min answer
4 terms in this topic
Fleet-Wide Change Reach
How long it takes a platform change to reach the majority of the services built on it - the measure of whether a platform can actually change anything.
toolService Scaffolding
Generating a new service with observability, CI, security and ownership already wired in, so the standard is the default rather than a checklist.
toolService Template
A generator that creates a new service already wired into the organisation's pipeline, telemetry, security and operational conventions.
practiceTemplate Propagation
The mechanism by which improvements to a service template reach the services already generated from it - the hardest part of the template model and t…
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.
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.
Platform Team Topologies
Stream-aligned, enabling, complicated-subsystem and platform teams, and their interactions.