Architecture, security & workflows

An architecture that splits a product into services with separate responsibilities. It is used when that split fits the way the system changes.

An architecture where parts of the system react to events instead of calling each other directly. It is used when work arrives as a series of events.

An approach that models software around the business domain. It is used when the domain rules are the hard part of the product.

An approach that separates commands that change data from queries that read it. It is used when those two paths need to differ.

A way to coordinate a business process that spans several services. It is used when one outcome depends on a series of steps.

An architecture of services that share a business process. It is used when the existing landscape is already organized that way.

A pattern that stops calling a dependency that is failing. It is used so one outage does not take down the caller.

A protocol for granting an application limited access to a protected resource. It is used when the product signs users in through another system.

A signed token format for passing claims between systems. It is used when a service needs to check who is calling.

An identity server for sign-in, tokens, and access. It is used when the product needs that kind of identity service.

A directory protocol for looking up people and groups. It is used when the company already keeps accounts there.

A way for a person to sign in once and reach several systems. It is used when the company already has that sign-in.

A workflow engine for business processes that people and services share. It is used when the process needs an explicit model.

An architecture where one product serves several customer organizations with separate data. It is used when those organizations share the product.