Platform engineering
Platform engineering is the discipline of designing and operating internal platforms that provide software teams with reusable capabilities and self-service workflows.
Effective Platform Engineering
An engineering platform is an internal development-oriented product that provides teams with self-service access to tools, infrastructure, and cross-functional capabilities while incorporating organizational requirements.
- How it is used
- Uses an internal product to remove delivery handoffs while giving developers self-service access to capabilities and organizational controls.
- How deep it goes
- Develops investment criteria, product ownership, domain boundaries, software-defined delivery, and adoption concerns rather than prescribing one finished platform design.
- Examples
- Uses a growing healthcare software company’s DNS, firewall, monitoring, and release handoffs to show why pipeline automation alone is insufficient.
- What you can do after
- Evaluate/understand when a platform is warranted, then apply product and software-engineering principles to design self-service capabilities.
Read how Effective Platform Engineering explains platform engineering →
Platform Engineering on Kubernetes
Platform engineering is the discipline of designing and operating internal platforms that provide reusable capabilities and streamlined workflows for software delivery teams.
- How it is used
- Enables development teams to deliver changes through shared workflows while a platform team manages tool choices and delivery automation.
- How deep it goes
- Works through tool integration, API-layer trade-offs, and a walking-skeleton delivery path, but leaves custom Kubernetes controllers outside the treatment.
- Examples
- Uses a multi-service Conference application, Helm installation, service and environment pipelines, and an environment-request API design.
- What you can do after
- Build it from scratch by selecting reusable tools, defining platform APIs, automating delivery workflows, and measuring whether changes help teams.
Read how Platform Engineering on Kubernetes explains platform engineering →
Developer Experience on Kubernetes
A software engineering discipline that builds internal platforms providing development teams with self-service capabilities while abstracting infrastructure complexity.
- How it is used
- Empowers development teams across the iterative journey from idea to value through self-service platform capabilities.
- How deep it goes
- Defines the discipline, Kubernetes implementation, API delivery, and infrastructure abstraction, but defers deeper platform treatment.
- Examples
- Uses Kubernetes-based platforms and on-demand developer services as implementation examples.
- What you can do after
- Evaluate how platform abstractions can reduce infrastructure interaction and improve developer productivity.
Read how Developer Experience on Kubernetes explains platform engineering →
Also covered in
- Software Security for Developers
- Architecture Modernization: Socio-technical alignment of software, strategy, and structure
What to know first
- authorizationAuthorization is the determination of which actions or resources an identity or other entity is permitted to access under defined permissions or policies.
- cloud-native architectureCloud-native architecture is an approach to designing and operating applications to exploit cloud infrastructure and services, including distributed operation, elasticity, and automated management.
- cloud providerA cloud provider is an organization or service operator that supplies remotely accessible computing resources or services over a network, often on demand.
- cognitive loadCognitive load is the mental effort required to process information, retain it in working memory, or perform a task.
Related concepts
- software engineeringkind of · Software engineering is the disciplined application of engineering principles, methods, and tools to the specification, development, operation, and maintenance of software.
- contractuses · A contract is an agreed specification of the conditions, expectations, rights, or obligations that govern behavior or interactions between parties or software components.
- decision treeused by · A decision tree is a tree-structured model or representation in which successive tests or choices lead through branches to outcomes, predictions, or actions.
- domain-driven designuses · Domain-driven design is a software design approach that centers models, structure, and terminology on the concepts, behavior, and boundaries of a problem domain.
- internal developer platformincludes · An internal developer platform is an organization-provided system of self-service interfaces, automation, abstractions, and reusable capabilities that supports software development and operation.
- self-serviceuses · Self-service is a mode in which users independently obtain resources or perform supported tasks without requiring an intermediary for each request.
Questions about platform engineering
What is platform engineering?
Platform engineering is the discipline of designing and operating internal platforms that provide software teams with reusable capabilities and self-service workflows.
Which Manning books explain platform engineering?
Effective Platform Engineering, Platform Engineering on Kubernetes and Developer Experience on Kubernetes.
What should I know before learning platform engineering?
Manning books that teach platform engineering usually introduce authorization, cloud-native architecture, cloud provider and cognitive load first.
What kinds of platform engineering are there?
Kinds of platform engineering include internal developer platform.
What is platform engineering a kind of?
Platform engineering is a kind of software engineering. Software engineering is the disciplined application of engineering principles, methods, and tools to the specification, development, operation, and maintenance of software.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.


