NimBus is a .NET integration platform on Azure Service Bus, with session ordering at each receiving endpoint, processing history in SQL Server or Cosmos DB, and an operator console for recovery. Deploy it in your own environment and connect applications through adapters.
A publisher drops one event on its endpoint's topic. NimBus's routing rules forward it to whoever consumes that type, delivers it to the handler in session order, and reports every state change to the Resolver.
Messages sharing a key are handled strictly in order. A poison message blocks only its own session — the rest of the bus keeps moving.
One centralized record of every message's outcome, start to finish. The recorded processing history is queryable from the operator console.
A live console to watch flows and resubmit or skip stuck messages — recover from failures without a redeploy.
You declare endpoints in code. NimBus provisions the topics, subscriptions, and routing rules to match — idempotently.
The kind of exception decides where the message goes. You configure the retry policy; NimBus routes the rest.
Configure the SDK, storage, pipeline, and receiver hosting through dependency injection. You bring the events and handlers; NimBus brings ordering, routing, storage, and recovery.
Plain classes. A [SessionKey] attribute sets the ordering scope for that event.
Declare what each endpoint produces and consumes; the Platform is the single source of topology truth.
Cosmos DB or SQL Server behind one contract — with a conformance suite keeping them honest.
Logging, metrics, validation — plus circuit-breaker, rate-limiting, and PII masking as opt-ins.
Record outgoing messages in your SQL business transaction; dispatch them after commit. Handlers should remain idempotent.
Run as a Worker or Azure Function.
AddNimBusPublisher / AddNimBusSubscriber
A schema registry with REST and MCP surfaces so AI agents can join the bus as first-class participants.
Failures, dead-letters, and session blocks fan out to webhook or email channels.