liveBook · Manning

Business criticality

As explained in Microservices Patterns, Second Edition

Business criticality is the degree to which a software capability is essential to an organization's business operations or value generation.

Business criticality describes how essential a software capability is to an organization’s operations or value generation. section 7.4.5

When subdomains differ in business criticality, isolating business-critical functionality in separate services can provide structural separation from the rest of the application. A monolith packages and deploys all subdomains together, limiting that separation. section 7.4.5 section 6.1.3

How Microservices Patterns, Second Edition covers it

How deep it goes
Names business criticality as a subdomain characteristic and notes isolation as an option, but gives no assessment criteria.
Examples
Uses business-critical functionality isolated from the rest of an application as an example, without naming a specific domain.
What you can do after
Evaluate whether differing subdomain characteristics warrant separate services rather than packaging everything together.
How it connects
Connects business criticality to subdomains, microservice architecture, and monolithic architecture.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.