https://juice-docs.creatorflow.io/core/messaging/local-transport/index.html Overview The Local Transport adds two in-process delivery routes and a unified IMessageService publishing interface. Messages can be dispatched to handlers within the same process without requiring a broker, while still supporting configuration-driven routing that can switch between local and broker delivery with no code changes. Route Publisher Key Durable? Latency Use case In-memory channel "local-channel" No Immediate Fast fire-and-forget: cache invalidation, lightweight side-effects Outbox + in-process "local" Yes Near-immediate Reliable cross-aggregate events within the same service Outbox + broker "rabbitmq" Yes Polling interval Cross-service messaging (existing) "local-channel" and "local" are mutually exclusive. If a publishing policy resolves both routes for the same event, "local" takes precedence — it is the durable superset (outbox write + immediate in-process dispatch). The "local-channel" route is ignored to prevent double handler invocation. Use one or the other per event type. Hugo en-us