Skip to content

The domain service integration pattern

In progress
50%
Owner
Sean with the integration architect
Due
20 November 2026
Scope
2.2
Updated
3 November 2026
Progress
from the status alone

as at 16 November 2026

Scope. Split by complexity: simple logic runs as an Azure Function App; a complex service with its own data model and lifecycle runs as a containerised service with its own store. Both expose a canonical contract, take synchronous calls through a domain service gateway of their own, publish events on Service Bus, and carry the same idempotency, retry, dead-letter, security and tracing rules. Each shape comes with a deployment template and a CI/CD template.

Achieved.

  • 3 Nov: drafted; whether a complex service is one multi-tier application or a set of microservices is the question the review settles.