How deeply does Effective Platform Engineering cover dedicated platform product code?

Explains the separation principle, its VPC application, and the change-cost consequences of cross-use-case coupling.

Dedicated platform product code

As explained in Effective Platform Engineering

Dedicated platform product code is infrastructure code whose scope is limited to provisioning and managing an engineering platform rather than unrelated enterprise use cases.

Dedicated platform product code provisions and manages only the engineering platform. Its structure and orchestration optimize the platform’s product experience and delivery service-level objectives, rather than supporting unrelated enterprise infrastructure use cases. section 7.2.1

Apply the pattern by:

Keeping platform infrastructure code separate from organization-wide infrastructure-as-code modules. section 7.2.1
Designing the VPC pipeline for engineering-platform VPCs only. section 7.2.1
Avoiding shared modules whose changes require testing against unrelated use cases and increase delivery time. section 7.2.1

Platform-only VPC pipeline

A VPC pipeline manages networks used by the engineering platform. Wrapping its implementation in an organization-wide VPC definition module would couple platform changes to unrelated enterprise consumers, making desired changes slower or impractical. section 7.2.1

How Effective Platform Engineering covers it

liveBook manning.com

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

Related concepts

evolutionary architectureuses · Evolutionary architecture is an architectural approach that preserves the ability to change through incremental implementation, validation, and refinement.

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.