liveBook · Manning

System integration

As explained in Platform Engineering on Kubernetes

The connection and coordination of separate software systems so they operate together as part of a larger system.

System integration connects separate tools, workflows, and services so they operate as composable parts of a larger platform. For development teams, these integrations enable continuous delivery and help organizations improve how they deliver software. section 1.1.2

In software delivery measurement, integration requires observing participating systems, capturing relevant data, aggregating it, and transforming it into metrics that expose bottlenecks. A durable design standardizes information consumption while allowing organizations to extend the model with additional metrics and sources. section 9.1.1

Common integration concerns include:

  • Combining internal workflows with external services such as Salesforce or other CRM systems. section 1.1.2
  • Connecting development systems to DORA-metric calculations through projects such as Four Keys or services such as LinearB. section 9.1.1
  • Using CloudEvents and CDEvents to standardize information exchanged across delivery systems. section 9.1.1
Figure 1.3 Organization-specific layers

Organization-specific layers help map integrations between shared platform capabilities and team workflows. section 1.1.2

How Platform Engineering on Kubernetes covers it

How deep it goes
Explains integration goals, data aggregation, and standardization but defers concrete implementation details to event standards.
Examples
Uses CRM systems, Four Keys, LinearB, CloudEvents, and CDEvents as integration examples.
What you can do after
Diagnose delivery bottlenecks by aggregating information from multiple systems into extensible performance metrics.
How it connects
Connects platforms, Kubernetes, cloud providers, DORA metrics, CloudEvents, CDEvents, and software delivery workflows.

Also explained in

Compare how 3 books explain system integration →

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.