liveBook · Manning

Contract

As explained in Acing the Frontend Interview

An API contract is a defined agreement describing the data shapes and interaction rules shared between software components or services.

In a domain-segmented frontend, versioned API/UI contracts help teams work and deploy independently while avoiding tight coupling and breaking changes. Shared API responses and components are examples of contracts to version. section 5.1

How Acing the Frontend Interview covers it

How deep it goes
Raises versioning shared API responses and components as a design question but does not specify a strategy.
Examples
Names API responses and shared components as contracts to version.
What you can do after
Evaluate versioning choices for shared API responses and components against the risk of breaking changes.
How it connects
Connects contracts with domain-based routing, team autonomy, independent deployment, and micro-frontends.

Also explained in

Compare how 58 books explain contract →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Acing the Frontend Interview. The section links point to the parts of the book it draws on.