Microservices architecture — Factory deltas¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
Filled 2026-10-09
This page (platform-foundations/microservices-architecture.md) was empty. Shared conventions (Clean Architecture layering, template composition, naming) live in ConnectSoft.Documentation and ADR-0009; this page records the Factory-specific deltas.
Modules before services¶
The 2026 catalog named 162 target services. The ownership map resolves them into 33 bounded contexts with one authoritative writer each and dispositions module / merge / external / conditional / defer. The initial physical shape is two application processes:
| Process | Hosts | Template |
|---|---|---|
| Control plane API | Project and scope, asset publication, run control and approvals, artifact metadata, policy enforcement, usage accounting modules | MicroserviceTemplate over BaseTemplate (canonical ADR-00xx layering) |
| Runtime worker | Common executor, model gateway pipeline, governed tool executor, context assembly | AgentTemplate (replacing its sample entry paths with the common execution contract) |
Existing identity, tenancy, persistence, messaging and telemetry foundations are infrastructure dependencies, not new services.
Extraction criteria¶
A module becomes a separate service only with a documented trigger (team ownership, trust boundary, measured load, release cadence or recovery need), a named new owner, state migration and backfill, event compatibility, authorization changes, latency and failure budget, deployment order and rollback. A parser, validator or event mapper alone is never sufficient. Two active writers for one capability are never a shortcut.
Store and transaction rules¶
Each owning module has its own schema even when several share one server; a worker never writes Control plane tables directly; transition and outbox records are written in one transaction of the selected messaging profile (Data & Event plane).
Reference consumer¶
DerechHaLev runs nine services (Gateway, AuthServer, Identity, six domain services) generated from the template estate, with Orleans silos per service and a custom BFF. It is the evidence that the conventions produce operable services, not evidence that the Factory's own services exist.