liveBook · Manning

Domain platform

As explained in Platform Engineering on Kubernetes

A platform designed to support the workflows and requirements of a particular organizational or business domain rather than general use.

A domain platform supports the workflows and requirements of a specific organizational or business domain. It optimizes tools and delivery practices for teams rather than providing generic capabilities. section 1.4.3

The platform grows from a realistic application and addresses the operational problems teams face when building, deploying, and running cloud-native services. Higher-level capabilities reduce the need to understand Kubernetes and its surrounding tools. section 1.4.3

Conference application walking skeleton

A Conference application provides a richer platform test case than a Hello World service. Its platform walking skeleton lets teams create features safely, work without conflicting with other teams, and evaluate whether new tools improve productivity. section 1.4.3

How Platform Engineering on Kubernetes covers it

How deep it goes
Traces a progression from application context through Kubernetes challenges to higher-level capabilities, deferring detailed tool treatment.
Examples
Uses a Conference application and a platform walking skeleton for safe feature development and experimentation.
What it assumes
Starts with a working application, then examines distributed applications and Kubernetes before adding platform capabilities.
What you can do after
Build it from scratch as higher-level capabilities that improve team productivity and reduce Kubernetes complexity.
How it connects
Connects domain platforms with cloud-native applications, distributed applications, Kubernetes, and platform engineering.

Also explained in

Compare how 2 books explain domain platform →

Related concepts

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