The sly squirrel that races up and down Yggdrasil, carrying slander and secrets between the eagle at the crown and NÃðhÃķggr at the roots â the original message broker.
Image credit: @norsemythologyclips â go follow them.
NServiceBus endpoint configuration, saga infrastructure, message conventions, and transport wiring for the Norse Architecture. Asgard declares the messaging surface; Ratatoskr carries it. The squirrel runs up and down Yggdrasil so the Ãsir never need to know how messages travel.
Norse.Messaging.* â the platform's messaging realm, scoped to all message-broker and transport activity, not just NServiceBus:
Norse.Messaging.NServiceBusis today's live vendor family â endpoint configuration, saga infrastructure, message conventions, and transport wiring â carved from Midgard for the same reason Urðarbrunnr was.- NServiceBus has strong opinions (sagas, message conventions, endpoint configuration) that
Norse.Infrastructureshould not be coupled to, and it has its own versioning and licensing lifecycle independent of the core abstractions. - A different broker or messaging library lands here as its own sibling under
Norse.Messaging.*(Norse.Messaging.MassTransit,Norse.Messaging.Rebus, âĶ) the same way Heimdall took on FluentUI â not every Midgardian implementation will use NServiceBus.
Asgard (Norse.Abstractions) declares the messaging surface â IPublishEvent<T>, ISendCommand<T>, IHandleMessage<T>, and the like â without caring how messages travel. Ratatoskr is the carrier.
A replacement for the messaging contracts in Asgard. Those stay put â the Ãsir declare the law; Ratatoskr just runs it.
This repo is a bare shell. No specs have converged here yet. The design process starts in Glitnir â brainstorm â spec â plan â code, in that order, never reversed. The full messaging decision (NServiceBus 10.2, ReceiveOnly transport transaction mode, source-generated handler registration, two endpoint flavors per context) is in Glitnir/docs/Platform/specs/2026-06-03-messaging-foundation-design.md.
