Modular Monolith with Wolverine Added in 1.2.0

Build a modular monolith with Wolverine: MultipleHandlerBehavior.Separated, MessageIdentity.IdAndDestination, IWolverineExtension for module registration, a module as an Event Model Domain ([Domain] on a handler or endpoint, model.Domain(name).Includes / IncludesNamespace policies, declared never inferred, one slice per module under Separated named OrderPlaced (Billing), and the ask-the-user rule when declarations disagree), inter-module messaging, module boundaries, and interactions with external brokers.

Use when multiple modules need to handle the same event types independently. Per-module stores work the same on Polecat and Fisher.

Skill details

• Skill name: critterstack-arch-modular-monolith
• Applies to: wolverine, marten, polecat, fisher
• Tags: architecture, modular-monolith, patterns, messaging, polecat, fisher, portability
• Added in: 1.2.0
• License: Proprietary. Copyright JasperFx Software LLC.

This skill is part of a paid product. The full content of critterstack-arch-modular-monolith (patterns, code examples, conventions, and guidance) is distributed only to licensed customers.

Buy AI Skills