Self-Service Provisioning
Self-service can reduce routine handling. Define what users receive, how partial failures are reconciled and who supports the capability after creation.
-
-
Service Catalog
A software catalog helps users discover owners and dependencies. Confirm responsibility, track ingestion gaps and connect records to support and workflows.
-
Parts of an Internal Developer Platform
A platform joins discovery, request fulfillment and continuing operation. Evaluate those capabilities separately and trace what happens after submission.
-
Platform Engineering
Platform engineering builds an internal product other teams consume, so common capabilities are paved once instead of rebuilt by every team that needs them.
-
Data Platforms vs. Developer Platforms
Four things get called a platform. See what each one hides, which capabilities data and developer platforms share, and how to draw the line of responsibility.
-
Platform as a Product
Understand users, maintain a roadmap, and evaluate task outcomes. Voluntary adoption adds evidence where choice exists; mandated platforms still need product management.
-
Golden Path
A golden path packages supported choices for a common task. State its scope, required controls, and the approval and support agreement for alternatives.
-
Internal Developer Platform
An internal developer platform is what a platform team ships — integrated capabilities offered through self-service interfaces, with defaults, guardrails, and a support commitment.
-
Golden Paths and Service Contracts
A golden path works when the platform and its users share a written contract. This article covers the consumer journey, templates, supported options, exceptions, and contract tests.
-
Platform Engineering: Consumers and Services
Start from the consumer’s task, not the mechanism: define the capability boundary, assign ownership, write a checkable self-service contract, and validate it with a runnable example.