Rebus
Topper
| Rebus | Topper | |
|---|---|---|
| 16 | 1 | |
| 2,235 | 26 | |
| 0.5% | - | |
| 8.4 | 0.0 | |
| 9 days ago | over 3 years ago | |
| C# | C# | |
| GNU General Public License v3.0 or later | 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
-
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:
Topper
-
Long-running business processes in F# with Rebus on Azure
As you know, we're using Topper so that we can easily run our Rebus back end in the Azure App Service as continuous Web Job. This means we need to have the App Service configured as always on. We need to create a database for Rebus to use, but we're Rebus will create the tables if they don't already exist. The same is true for the queues in our Azure Service Bus. We need to change our configuration spells a little so that we can use these Azure resources.
What are some alternatives?
MassTransit - Distributed Application Framework for .NET
TopShelf - An easy service hosting framework for building Windows services using .NET
NServiceBus - Build, version, and monitor better microservices with the most powerful service platform for .NET
AzureSTTService - A simple Windows Background service in C# code, to perform subsequent Speech-To-Text (STT) process on wave files, using Azure Speech Services
RabbitMQ.NET - RabbitMQ .NET client for .NET Standard 2.0+ and .NET 4.6.2+
Kafka Client
BedrockManagementService - A multiple host, multiple server, Minecraft bedrock server management service and GUI manager.
EasyNetQ - An easy to use .NET API for RabbitMQ
RebusSamples - Small sample projects
CAP - Distributed transaction solution in micro-service base on eventually consistency, also an eventbus with Outbox pattern
Serilog - Simple .NET logging with fully-structured events