Module Architecture Patterns

Module-level patterns describe how a complete module is structured across all of its layers, in contrast to the layer-specific patterns under persistence, api, and service. A module page is the hub that refers down to the layer-specific specializations (bitemporal logic in persistence, transaction boundaries in service) for detail.

Pages in this section

• Data Authority Module Pattern — the primary four-layer module pattern (Protocol Adaptor → Service → Persistence → Proxy) for modules that own and manage a set of entities, with the Cross-Service Isolation rule.

See also

• Design Pattern Index — the parent catalog of architectural patterns.
• Module Concept — the general module abstraction (state encapsulation, endpoints, bindings) that the Data Authority Module specializes.