monica-business-microservice

What problem does it solve?

Guides architects and developers to correctly structure Monica DDD microservices, decide where each subdomain and contract belongs, and prevent dependency leakage or collapsing service boundaries.

Core Features & Use Cases

• Solution layout guidance: Prescribes a canonical src/ layout with AppHost, Shared platform layers, Services, and Migrations to keep ownership clear.
• Project reference rules: Enforces the strict chain API -> Domain -> Platform.Infrastructure -> Platform.Protocol -> Platform.BuildingBlocks and where to place project-common versus service-only libraries.
• Contract and collaboration patterns: Advises what belongs in PublishedLanguages, when to prefer events vs synchronous calls, and how to keep APIs as adapters.
• Operational checklist: Provides a step-by-step workflow for creating new subdomains, wiring migrations, and final delivery checks to ensure migration ownership and host registration order.

Quick Start

Design a new subdomain service named Ordering and ask for a solution layout, the required PublishedLanguages entries, the API/Domain/migration project scaffolding, and a migration ownership checklist.