OpenSleigh
BlazorWorker
| OpenSleigh | BlazorWorker | |
|---|---|---|
| 6 | 6 | |
| 306 | 356 | |
| - | - | |
| 6.5 | 7.8 | |
| 8 months ago | 17 days ago | |
| C# | C# | |
| Apache License 2.0 | MIT License |
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.
OpenSleigh
-
Are Sagas hidden Monoliths?
If you're using .NET, you might want to check products like MassTransit, NServiceBus, Rebus or OpenSleigh(disclaimer: I'm the author of OpenSleigh :) )
-
UI notifications system with Blazor and SignalR - part 1
Hi All! Today we’re going to see how we can write a UI notification system. We will use Blazor to render the UI, SignalR to handle the client/server communication, and OpenSleigh to execute the background operations.
-
Dynamic method invocation with .NET Core
Anyways, while working on the first prototypes of OpenSleigh (BTW, make sure to at least fork or star the repository!), I had to face a bunch of times an interesting problem.
-
Is There A Mature Saga Framework In Net
you might want to take a look at this: https://github.com/mizrael/OpenSleigh
-
How to do Document-level locking on MongoDB and .NET Core
Just for you to know, a while ago I started working on OpenSleigh, a distributed saga management library for .NET Core. It uses the same technique in its MongoDB persistence driver.
-
OpenSleigh: a Saga management library for .NET Core
So don't hesitate! Take a look at the repository on GitHub, download the packages, play with them, and send me your feedback!
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
What are some alternatives?
Rebus - :bus: Simple and lean service bus implementation for .NET
micro-bootstrap - A Full Stack framework written in .NET Core to speed up your development process in microservices and modular monolith apps. It gathers most widely used frameworks in .NET world and pack them into a simple bootstrap package.
silverback - Silverback is a simple but feature-rich message bus for .NET core (it currently supports Kafka, RabbitMQ and MQTT).
MassTransit - Distributed Application Framework for .NET
RawRabbit - A modern .NET framework for communication over RabbitMq
FluentMediator - :twisted_rightwards_arrows: FluentMediator is an unobtrusive library that allows developers to build custom pipelines for Commands, Queries and Events.
HostedServiceDemo
Cleipnir.Flows - Simply making fault tolerant code simple
EventFlow - Async/await first CQRS+ES and DDD framework for .NET
DotNet.ApiRest.BasicTemplate - Build an simple API Rest project using best practices, professional componentes: Swagger, Serilog, Entity Framewokr, Authentication (AAD), Azure Aplication Insight, Docker, Kubernetes, Helm, Azure Pipelines and much more.
BenchmarkDynamicInvocation