liveBook · Manning

Domain platform

A domain platform provides reusable capabilities and workflows for products or teams within a particular business or organizational domain.

How 2 Manning books explain it

Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A horizontal is a shared business or technical capability that serves multiple verticals.

How it is used
Frames reuse and centralization decisions for organizations with multiple products, verticals, or markets.
How deep it goes
Explains economies of scale, bottlenecks, and governance trade-offs, but stops short of implementation detail.
Examples
Uses Uber fulfillment, BBC horizontal domains, shared booking, centralized identity, and centralized-versus-decentralized macrostructures.
What you can do after
Evaluate centralization choices and map shared capabilities against user experience, demand, funding, dependencies, and delivery speed.

Read how Architecture Modernization: Socio-technical alignment of software, strategy, and structure explains domain platform →

Platform Engineering on Kubernetes

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

How it is used
Optimizes tools and workflows for teams delivering services in a specific domain.
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 you can do after
Build it from scratch as higher-level capabilities that improve team productivity and reduce Kubernetes complexity.

Read how Platform Engineering on Kubernetes explains domain platform →

Related concepts

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.