orleans-multiservice-pattern

To organize multiple logical services inside a single Orleans silo, use a modular monolith pattern that enforces a three-project structure for each service, comprising Apis, Contracts, and Service components with constrained access boundaries.

The MonolithFirst architecture pattern for .NET Orleans backends hosts multiple logical services within a unified silo, establishing clean dependency boundaries that enable cheap and future-ready extraction into separate microservices.

To structure a new Orleans service for future microservice extraction, apply a three-project structure consisting of Apis.<Service>Api, Contracts.<Service>Contract, and <Service>Service to maintain strict dependency separation.

Yes, you can add a new logical service to an existing Orleans multiservice silo by using the optional AddLogicalService.ps1 script to extend the multiservice architecture while preserving clean dependency boundaries.

You should choose a modular monolith over separate microservices for new Orleans backends when adopting a MonolithFirst strategy, allowing you to delay distributed deployment costs while preserving the ability to extract services later.