liveBook · Manning

Domain

As explained in Google Anthos in Action

A business domain is a bounded area of business knowledge, rules, data, and capabilities addressed by software.

A business domain is a focused area of business capability that can be separated from a legacy application and implemented as an independently developed service. Clear boundaries and well-known contracts limit the impact of changes on dependent services. section 16.1

Use domain boundaries to:

  • Build and test one business capability in isolation for faster iteration. section 16.1
  • Extract capabilities incrementally instead of rewriting the entire application when investment and business goals favor a gradual transition. section 16.1
  • Start modernization with edge capabilities such as authentication, authorization, or logging. section 16.1

Incremental extraction

Separate an authentication capability from a legacy application, expose it through a well-known contract, and operate it as a cloud-native service while other capabilities remain in the monolith. section 16.1

How Google Anthos in Action covers it

How deep it goes
Explains isolation, service contracts, incremental extraction, and rewrite trade-offs without detailing domain-modeling techniques.
Examples
Uses authentication, authorization, and logging as capabilities that can be extracted first from a legacy application.
What you can do after
Apply it by isolating and extracting a business capability into a service with a stable contract.
How it connects
Connects business domains with microservices, service contracts, authentication, authorization, logging, and serverless architecture.

Also explained in

Compare how 5 books explain domain →

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.