How deeply does Google Anthos in Action cover breaking change?

Frames detection at the contract boundary without detailing compatibility rules or migration procedures.

Breaking change

A breaking change is a modification to an interface or behavior that can cause existing dependent clients or services to fail.

A breaking change crosses a service contract boundary in a way that can affect dependent services. Standard contracts make that boundary visible while capabilities are separated from a legacy application. section 16.1

Use contract boundaries to manage modernization risk:

Define well-known contracts between independently deployable business-domain services. section 16.1
Test an extracted or rewritten capability in isolation before changing dependent services. section 16.1
Prefer incremental extraction when business goals and investment appetite favor smaller modernization steps. section 16.1

How Google Anthos in Action covers it

liveBook manning.com

Read Google Anthos in Action on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Automating API DeliveryA breaking change is an API modification that can cause existing consumers or integrations to stop working.
liveBook manning.com

Go in Action, Second EditionA breaking change is a modification that can prevent existing consumers from continuing to work without updates.
liveBook manning.com

Terraform in Depth: Infrastructure as Code with Terraform and OpenTofuA breaking change is a software change that makes previously valid code, configuration, or interfaces require modification to function correctly.
liveBook manning.com

Building Web APIs with ASP.NET CoreA breaking change is a modification that can cause existing clients or system integrations to stop working correctly.

Compare how 5 books explain breaking change →

Related concepts

backward compatibilitycontrasts with · Backward compatibility is the property of a changed or newer system remaining usable by existing clients and consumers of its earlier interfaces, behavior, or data.
versioningaddressed by · The practice of identifying and managing successive revisions of files, data, models, interfaces, or other artifacts so changes can be tracked and earlier states recovered.
major versionproduces · A major version is the primary component of a version identifier that distinguishes a release line and commonly signals potentially backward-incompatible changes.
review processaddressed by · A review process is a structured evaluation of work, performance, artifacts, or proposals against relevant criteria to assess quality, progress, correctness, or suitability.
sunset strategyincludes · A sunset strategy is the planned discontinuation and shutdown of a software component, such as an API or subsystem, after its supported service period.

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.