Platform service

As explained in Effective Platform Engineering

A platform service is a cluster capability deployed as part of standard cluster configuration without exposing a uniquely provisionable resource type to developers.

A platform service is a cluster capability deployed through standard cluster configuration rather than exposed as a uniquely provisionable resource type for developers. This distinction separates platform-wide capabilities from extensions. section 8.2

Platform services provide the safer first boundary for distributing ownership as adoption grows. Teams can move service responsibilities beyond the core platform product organization before considering extensions, which should wait until the platform is beyond its MVP and has meaningful adoption. section 8.2

Operational implications include:

• Use separate release orchestration pipelines as services and extensions scale, while deploy-event automation remains local to the cluster. section 8.2
• Treat the service-versus-extension boundary as an organizational scaling aid, not merely as a way to configure technology for higher load. section 8.2

Figure 8.2 The easiest way to understand the difference is to focus on extensions. When deployed, an extension enables developers to provision a resource through the Kubernetes API that Kubernetes does not natively support.

Compare a platform service with an extension: an extension enables developers to provision a non-native resource through the Kubernetes API. section 8.2

How Effective Platform Engineering covers it

How deep it goes

Defines services by contrast with extensions and discusses pipelines and ownership, but does not detail service implementation internals.

Examples

Uses release orchestration pipelines and local cluster deploy-event automation as operational examples.

What you can do after

Evaluate ownership boundaries and sequence service delegation before extension delegation as adoption grows.

How it connects

Connects platform services with extensions, Kubernetes API resources, cluster-wide applications, and platform product leadership.

liveBookmanning.com

Read Effective Platform Engineering on liveBook Get the book at manning.com

Related concepts

• autocompleteused by · Autocomplete is an interactive input feature that suggests or completes likely continuations of partially entered text, code, commands, or other values.
• database serviceincludes · A database service is a software or cloud service that provides managed storage, organization, querying, and retrieval of application data.
• rate limitincludes · A rate limit is a bound on the frequency or volume of operations permitted within a defined interval, scope, or concurrency limit.
• platform extensioncontrasts with · A platform extension is a cluster capability that extends the Kubernetes API by exposing a new resource type or developer-configurable experience.
• control planeincludes · A control plane is the management and coordination part of a system that governs the configuration, policies, state, and operations of its components and resources.

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.