🚌 Simple and lean service bus implementation for .NET
Alternatives To Rebus
Project NameStarsDownloadsRepos Using ThisPackages Using ThisMost Recent CommitTotal ReleasesLatest ReleaseOpen IssuesLicenseLanguage
Cap6,170102482 days ago200July 30, 20236mitC#
Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern
Rebus2,10692166a month ago515August 23, 202321otherC#
:bus: Simple and lean service bus implementation for .NET
Liquid Application Framework493
25 days ago1September 09, 202218mitC#
Liquid Application Framework documentation, useful links and sample project
Cqrs3374367 months ago292October 21, 2022108lgpl-2.1C#
A lightweight enterprise Function as a Service (FaaS) framework to write function based serverless and micro-service applications in hybrid multi-datacentre, on-premise and Azure environments.
Obvs33311252 years ago41November 17, 20214mitC#
An observable microservice bus library for .NET, that wraps the underlying message transports in simple Rx based interfaces.
Silverback22111019 days ago135February 21, 202320mitC#
Silverback is a simple but feature-rich message bus for .NET core (it currently supports Kafka, RabbitMQ and MQTT).
Event Sourcing Jambo182
5 years agoapache-2.0C#
An Hexagonal Architecture with DDD + Aggregates + Event Sourcing using .NET Core, Kafka e MongoDB (Blog Engine)
a day ago93mitTypeScript
Build scalable and durable micro-services with APIs, Messaging and Workflows
Temporal Go Helpers29
3 months ago4November 02, 20211mitGo
:arrows_clockwise: Common convenience methods, and developer ergonomics for Temporal's Go SDK.
Servicebus Microservice18
3 years ago1JavaScript
A boilerplate for building microservices with servicebus
Alternatives To Rebus
Select To Compare

Alternative Project Comparisons


Latest stable: NuGet stable

Current prerelease: NuGet pre

Tests: Build status

This repository contains Rebus "core". You may also be interested in one of the many integration libraries.

For information about the commercial add-on (support, tooling, etc.) to Rebus, please visit Rebus FM's page about Rebus Pro.


Rebus is a lean service bus implementation for .NET. It is what ThoughtWorks in 2010 called a "message bus without smarts" - a library that works well as the "dumb pipes" when you need asynchronous communication in your microservices that follow the "smart endpoints, dumb pipes" principle.

Rebus aims to have

  • a simple and intuitive configuration story
  • a few well-selected options
  • no doodleware
  • as few dependencies as possible (currently only JSON.NET)
  • a broad reach (targets .NET Standard 2.0, i.e. .NET Framework 4.6.1, .NET Core 2, and .NET 5 and onwards)
  • integration with external dependencies via small, dedicated projects
  • the best error messages in the world
  • a frictionless getting-up-and-running-experience

and in doing this, Rebus should try to align itself with common, proven asynchronous messaging patterns.

Oh, and Rebus is FREE as in beer 🍺 and speech 💬, and it will stay that way forever.

More information

If you want to read more, check out the official Rebus documentation wiki or check out my blog.

You can also follow me on Twitter: @mookid8000

Getting started

Rebus is a simple .NET library, and everything revolves around the RebusBus class. One way to get Rebus up and running, is to manually go

var bus = new RebusBus(...);
bus.Start(1); //< 1 worker thread

// use the bus for the duration of the application lifetime

// remember to dispose the bus when your application exits

where ... is a bunch of dependencies that vary depending on how you want to send/receive messages etc. Another way is to use the configuration API, in which case you would go

var someContainerAdapter = new BuiltinHandlerActivator();

for the built-in container adapter, or

var someContainerAdapter = new AdapterForMyFavoriteIocContainer(myFavoriteIocContainer);

to integrate with your favorite IoC container, and then

    .Logging(l => l.Serilog())
    .Transport(t => t.UseMsmq("myInputQueue"))
    .Routing(r => r.TypeBased().MapAssemblyOf<SomeMessageType>("anotherInputQueue"))

// have IBus injected in application services for the duration of the application lifetime    

// let the container dispose the bus when your application exits

which will stuff the resulting IBus in the container as a singleton and use the container to look up message handlers. Check out the Configuration section on the official Rebus documentation wiki for more information on how to do this.

If you want to be more specific about what types you map in an assembly, such as if the assembly is shared with other code you can map all the types under a specific namespace like this:

    .Routing(r => r.TypeBased().MapAssemblyNamespaceOf<SomeMessageType>("namespaceInputQueue"))

// have IBus injected in application services for the duration of the application lifetime    

// let the container dispose the bus when your application exits


Rebus is licensed under The MIT License (MIT). Basically, this license grants you the right to use Rebus in any way you see fit. See for more info.

The purpose of the license is to make it easy for everyone to use Rebus and its accompanying integration libraries. If that is not the case, please get in touch with [email protected] and then we will work something out.

Popular Service Bus Projects
Popular Microservices Projects
Popular Control Flow Categories
Related Searches

Get A Weekly Email With Trending Projects For These Categories
No Spam. Unsubscribe easily at any time.
C Sharp
Message Queue
Message Bus
Service Bus
Messaging Library