Federated services on a shared hub.
Connect distinct services through a shared layer for identity, context, observability, and recourse while each service retains its own operating boundary.
Operating pattern
A multi-service operating environment can expose separate interfaces, data, and onboarding paths for work that depends on the same shared context. Replacing every service with one platform would also erase boundaries that may need to remain distinct.
The design problem is to unify the interaction and context layer without pretending the underlying services are one system.
Capability pattern
Create a shared hub for identity, context, observability, and recourse, then connect each service through a governed interface. Services retain their operational ownership while the hub carries the common interaction contract.
New services can be added against the same contract, with access and escalation boundaries defined for each one.
What the pattern enables
The pattern connects workflows and trust. Cross-service routes have a common context and trace, while each service remains accountable for the work inside its own boundary.