rebus-onboardingcs
Rebus
| rebus-onboardingcs | Rebus | |
|---|---|---|
| 1 | 16 | |
| 5 | 2,235 | |
| - | 0.5% | |
| 5.4 | 8.4 | |
| 23 days ago | 10 days ago | |
| C# | C# | |
| - | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rebus-onboardingcs
-
Long-running business processes in F# with Rebus on Azure
Aside: There are two versions of this post - one using C# and one using F#. Just for fun, why not try running the API from the C# project and the backend from the F# project? As long as you're using the same transport (at this stage that's a file system in c:\rebus-advent) then everything will work just fine. How lovely is that? :)
Rebus
-
Message Queueing
I can recommend Rebus: https://github.com/rebus-org/Rebus – it’s the one I know best, because I made most of it 🤠 and it even has a Pro option, if you feel like upgrading in that direction too some time in the future.
-
how do you develop locally using Azure Service Bus?
The whole trick is that that's the headache of the implementor of the abstraction 😅 (e.g. me, if you're using Rebus).
-
Agnostic Messaging Provider - Azure/Google/AWS
Rebus (https://github.com/rebus-org/Rebus)
- Which library do you use for message bus abstraction?
-
Pub Sub Framework Recomendations?
For multiprocess application (multiple services, containerized and also natives) I've used ReBus (https://github.com/rebus-org/Rebus) which was is API-compatible (for some version) with NServiceBus. We first used NServiceBus with RabbitMQ (Sagas stored in SqlServer) and then after migration to ReBus also messages and queues were in SqlServer.
-
Long-running business processes in F# with Rebus on Azure
Then we add the Rebus and Rebus.ServiceProvider NuGet packages to each project, giving us something like this:
What are some alternatives?
Topper - :tophat: Simple Windows Service helper (Topshelf-based, Azure Web Job capable)
MassTransit - Distributed Application Framework for .NET
Serilog - Simple .NET logging with fully-structured events
NServiceBus - Build, version, and monitor better microservices with the most powerful service platform for .NET
RabbitMQ.NET - RabbitMQ .NET client for .NET Standard 2.0+ and .NET 4.6.2+
Kafka Client
EasyNetQ - An easy to use .NET API for RabbitMQ
CAP - Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
Brighter - A framework for building messaging apps with .NET and C#.
OpenSleigh - OpenSleigh is a Saga management library for .NET Core.
MediatR - Simple, unambitious mediator implementation in .NET