Session-ordered processing
Messages sharing a key are handled strictly in order. A poison message blocks only its own session; the rest of the bus keeps moving.
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 sends one event to its endpoint's topic. Routing rules forward a copy to every endpoint that consumes that type, the receiver hands it to your handler in session order, and each outcome is reported to the Resolver.
The producer sends one event to its own endpoint topic.
Rules keyed on the event type forward a copy to each consuming endpoint. Forwarded copies are never forwarded again.
Messages with the same session key are handled one at a time, in order.
Your handler processes the event.
The message completes, or follows one of the failure paths below.
The Resolver receives every outcome and keeps one queryable record of each message's status, from Pending to Completed or Failed.
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, so you recover from failures without a redeploy.
You declare endpoints in code. NimBus provisions the topics, subscriptions, and routing rules to match, idempotently.
What the handler throws decides where the message goes. You configure retry policies and failure classifiers; NimBus routes the rest.
The handler throws TransientException, for example
after a timeout or a 503. The message is abandoned and Service
Bus redelivers it.
A bad payload or an unrecoverable 4xx, classified as permanent. The message goes straight to the dead-letter queue without using retries.
Any other exception fails the message and blocks its session. A matching retry policy schedules a retry; otherwise the session waits for an operator to resubmit or skip.
A failure classifier can discard it. The message completes without a retry or a dead-letter, and the session carries on.
The handler hands the work off to an external system. The session waits, in order, until the work completes or fails.
Messages that arrive behind a blocked message are recorded as Deferred and replay in order once the session is unblocked. The Resolver's main statuses are Pending, Completed, Failed, Deferred, Dead-lettered, and Skipped.
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. [SessionKey] sets the ordering scope,
and [Sensitive] masks a property for operators
without PII access.
Declare what each endpoint produces and consumes. The platform definition is the single source of topology truth.
SQL Server or Cosmos DB behind one contract, with a conformance suite keeping them honest.
Logging, metrics, and validation are built in. An opt-in circuit breaker pauses an endpoint when its failure rate spikes.
Record outgoing messages in your SQL business transaction and dispatch them after commit. Handlers should remain idempotent.
Run handlers in a .NET Worker or an Azure Function, registered
with AddNimBusPublisher and
AddNimBusSubscriber.
A schema registry and REST agent API let AI agents join the bus; the operator MCP endpoint lets them investigate and recover failures.
Failures, dead-letters, and session blocks fan out to webhook, Teams, or email channels.
nb setup chains Bicep infrastructure, topology
provisioning, and app deployment, in that order.
Deployment guide → · CLI reference → · Architecture → · Decision records →
The CRM/ERP sample runs the whole platform on your machine, with no Azure account needed.