Rebus alternatives and similar packages
Based on the "Queue" category.
Alternatively, view Rebus alternatives based on common mentions on social networks and blogs.
Confluent's Apache Kafka .NET client
MediatR extension for SimpleInjector with samples for ASP.NET Core and full ASP.NET
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of Rebus or a related project?
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 4.5, .NET 4.6, and .NET Standard 2.0, i.e. full .NET fx and .NET core)
- 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.
You can also follow me on Twitter: @mookid8000
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 bus.Dispose();
... 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
Configure.With(someContainerAdapter) .Logging(l => l.Serilog()) .Transport(t => t.UseMsmq("myInputQueue")) .Routing(r => r.TypeBased().MapAssemblyOf<SomeMessageType>("anotherInputQueue")) .Start(); // have IBus injected in application services for the duration of the application lifetime // let the container dispose the bus when your application exits myFavoriteIocContainer.Dispose();
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.
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.
*Note that all licence references and agreements mentioned in the Rebus README section above are relevant to that project's source code only.