modular-monolith

To isolate bounded contexts in a modular monolith, structure each module as a self-contained unit with its own domain, data ownership, and public API contracts. This approach prevents tangled dependencies by enforcing strict module boundaries and dedicated registration extensions.

The best way to communicate between modules in a .NET modular monolith is through event-driven integration. Modules interact asynchronously using integration events and well-defined public contracts to maintain data consistency without leaking domain logic.

Yes, you need a separate DbContext for each module in a modular monolith to ensure module-owned data and independent data ownership. Per-module configurations and dependency injection registrations are applied to maintain this isolation.

You need a shared kernel in a modular monolith when you require a minimal shared layer for cross-cutting types and base entities across bounded contexts. It hosts these shared types without leaking specific domain logic into other modules.

To structure a new module in a .NET modular monolith, create a self-contained unit under the Modules directory implementing its Api, Core, and Infrastructure layers. Finally, register the module in the host application to run the modular monolith.

Use public API contracts for inter-module communication to enable safe interactions between modules without creating tangled direct dependencies. Well-defined interfaces maintain strict architectural boundaries and allow modules to evolve independently within the modular monolith.