BlazorWorker
Rebus
| BlazorWorker | Rebus | |
|---|---|---|
| 6 | 16 | |
| 358 | 2,239 | |
| - | 0.7% | |
| 7.8 | 8.4 | |
| 29 days ago | 19 days ago | |
| C# | C# | |
| MIT License | 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.
BlazorWorker
- Multithreading support pushed to .net 9
- Running a background process on a timer for Blazor WASM in .Net 6
- High CPU tasks and scaling
- Run background tasks in blazor wasm like worker
-
For client-side Blazor (WASM), how do you handle long-running, CPU-bound tasks?
I've given BlazorWorker a try in order to get this running in a separate thread/in the background, but it didn't seem to help here. Do I have any options other than to convert this to an ASP.NET hosted app and do the heavy lifting on the server?
-
Improve Lighthouse Performance
Another possible option is to use web workers for parts of your application that are more demanding. See this library for more info and demos: https://github.com/Tewr/BlazorWorker
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?
OpenSleigh - OpenSleigh is a Saga management library for .NET Core.
MassTransit - Distributed Application Framework for .NET
silverback - Silverback is a simple but feature-rich message bus for .NET core (it currently supports Kafka, RabbitMQ and MQTT).
NServiceBus - Build, version, and monitor better microservices with the most powerful service platform for .NET
RawRabbit - A modern .NET framework for communication over RabbitMq
RabbitMQ.NET - RabbitMQ .NET client for .NET Standard 2.0+ and .NET 4.6.2+
HostedServiceDemo
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#.