liveBook · Manning

Contract

As explained in Google Anthos in Action

An API is a defined interface through which software components communicate and access capabilities or data.

A contract defines a boundary between services, making their responsibilities explicit. In a microservices design, standard contracts help identify changes that could break dependent services. section 16.1

Clear boundaries let teams build and test a business-domain service in isolation, supporting faster iteration of its capabilities. section 16.1

Incremental service extraction

When modernizing a legacy application, teams may start by extracting capabilities such as authentication, authorization, or logging into separate services. section 16.1

How Google Anthos in Action covers it

How deep it goes
Connects contracts to breaking-change detection and isolated domain testing without specifying contract formats.
Examples
Names authentication, authorization, and logging as capabilities teams may extract into separate services.
What you can do after
Apply standard contracts to identify potentially breaking service changes and test business-domain services independently.
How it connects
Links contracts with APIs, microservices, and application modernization.

Also explained in

Compare how 44 books explain contract →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.