NimBus documentation
NimBus is an open-source .NET integration platform on Azure Service Bus. It connects business systems with session-ordered processing, tracks every message through a central Resolver, and gives operators a management WebApp to investigate failures and resubmit or skip blocked work.
Start here
| If you want to | Read |
|---|---|
| Run NimBus on your machine | Getting started |
| See what the platform does | Features |
| Understand the components and how they fit | Architecture |
| Take a customer project from zero to go-live | Onboarding a customer project |
How it works
- Message flows covers how messages move through the Service Bus topology.
- Error handling covers retries, dead-lettering, and resubmit or skip.
- Deferred messages covers how a blocked session parks and replays work.
- Consumer inbox covers idempotent handling of redelivered messages.
- Pending handoff covers long-running work completed outside the handler.
- Orchestration covers multi-step processes without a saga framework.
- Circuit breaker and Platform heartbeat cover endpoint health.
Build integrations
- Building adapters is the main guide for publishers, handlers and hosting.
- Azure Functions hosting covers subscribers on Azure Functions.
- Pipeline middleware covers cross-cutting behaviors around handlers.
- Testing covers the in-memory transport and the test fixture.
- Extensions, Notification channels and Integration Intelligence cover the optional packages.
- CloudEvents interoperability and AsyncAPI mapping cover working with systems that do not use NimBus.
Deploy and operate
- Azure requirements and Deployment cover the infrastructure and the pipelines.
- Private networking and Authentication and identity cover network isolation and access.
- Storage providers covers Cosmos DB and SQL Server.
- Rate limiting and Throughput tuning cover load.
- Operator MCP server covers operating NimBus from an AI agent.
- Reconciling stale Pending rows and Service Bus subscriptions are incident runbooks.