MediatR
Hangfire
MediatR | Hangfire | |
---|---|---|
53 | 61 | |
10,614 | 9,013 | |
- | 0.5% | |
6.2 | 9.4 | |
14 days ago | 10 days ago | |
C# | C# | |
Apache License 2.0 | 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.
MediatR
-
The Monad Invasion - Part 2: Monads in Action!
You probably noticed that .SetName() returns a Either. You may have come across Unit in libraries like MediatR or Language-Ext. It's a simple construct representing a type with only one possible value. We use it as a placeholder for operations that do not return a value but may return another state. In our example, .SetName() is a Command that does not return a value but may fail. Therefore, the monad Either carries two possible states: Right (without value) or Left (with an Error).
-
How small is the smallest .NET Hello World binary?
The widely used MediatR library[0] could be used to do that as well, just FYI.
[0]: https://github.com/jbogard/MediatR
- Cannot use disposed service
- Exception handling between controller and service
-
CQRS: How to handle duplicate queries inside a CommandHandler
Hope this GH issue shed some light on why injecting handler inside another handler is not good https://github.com/jbogard/MediatR/issues/400
-
Is MediatR the only real CQRS solution for .Net?
From: https://github.com/jbogard/MediatR
-
Easiest way to build the fastest REST API in C# and .NET 7 using CQRS
I gave it a go and I was impressed how easy and fast it was to set it all up. Since I'm not a big fan of REPR pattern almost all my projects are using CQRS pattern with a help of MediatR ](https://github.com/jbogard/MediatR) I immediately started going over something similar that Fast Endpoints offer which is a command bus.
-
MVVM Question: How do you manage the interaction between Model and ViewModel?
I'd use a dedicated event bus based on Reactive Extensions or MediatR to publish domain events from your domain services. This probably doesn't solve all your ViewModel update problems as is, maybe you need to revise the granularity (maybe you can have smaller ViewModels that refresh single property that exposes the Model) and lifespan (sometimes you can create a ViewModel, make it perform it's task and then discard it completely) of your ViewModels.
-
Async Methods after setting a property.
If you're finding yourself in a situation where you need to turn this behavior into a pattern because there are a lot of View Models that need to execute async business logic in response to some changes, I'd go with something like MediatR or Reactive Extensions. The idea is, again, that some other, probably business-level, component listens to changes in a decoupled way (that means it doesn't subscribe directly to your View Model, but to an event bus instead). View Model publishes change events to the event bus, and business-component reacts to these events by executing the business logic.
-
I don't get why I should use Redux
What people really want is to design the logic of an app independently from the component hierarchy. That means you need to store state somewhere other than the components and you need to dispatch events that are not attached to the component hierarchy. Also, a one way data flow has well known benefits as described by things like CQRS, RabbitMQ, and MediatR.
Hangfire
-
Deno Cron
Unpopular opinion incoming... What I see is yet another way that the backend JS world is finally achieving something .NET had years ago[0].
Node/Deno/Bun/etc. + npm sounds super straightforward at first glance (and it is at first). But I've thought for years that it's far easier to be productive as an organization on .NET in Visual Studio, since it's simpler to design, deliver, and maintain infrastructure.
[0] https://www.hangfire.io/
-
Boosting Productivity with HangFire: Streamlining Background Job Processing
you can read about it here HangFire Documentation
-
How do you save a file at the end of the day within a function that is only called at certain times?
I mostly work in .NET, and typically use Hangfire, but all languages has similar frameworks
-
What can I use as a simple message bus with persistence in .NET?
Its hard to tell what tool would be a best fit without more information, but I would suggest looking at Hangfire for background job processing: https://www.hangfire.io/
-
Event Bus + Job APIs
You might want to look at https://www.hangfire.io/. Their docs explain how to set up queues: https://docs.hangfire.io/en/latest/background-processing/configuring-queues.html
-
Background Job Scheduling in .NET using Hangfire
In this article we looked at how to use Hangfire to schedule background jobs in ASP.NET according to our requirements. In a follow up article, I will talk about using Hangfire with a Redis storage. To learn more about Hangfire, you can visit the official website.
-
BackgroundService in .Net Core
Easy to understand if you want to implement your own background service. If you want a more easy and complete tool you can use hangfire.
-
Is there anything like this in C#?
Try https://www.hangfire.io/
-
Help in creating a new Service
If, as you stated, you really need to use your own servers, that seems exactly like a job for Hangfire.
- Background processing in .NET MAUI app
What are some alternatives?
Mediator.Net - A simple mediator for .Net for sending command, publishing event and request response with pipelines supported
QuartzNet - Quartz Enterprise Scheduler .NET
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
RabbitMQ.NET - RabbitMQ .NET client for .NET Standard 2.0+ and .NET 4.6.2+
Polly - Polly is a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner. From version 6.0.1, Polly targets .NET Standard 1.1 and 2.0+.
MassTransit - Distributed Application Framework for .NET
Brighter - A framework for building messaging apps with .NET and C#.
Coravel - Near-zero config .NET library that makes advanced application features like Task Scheduling, Caching, Queuing, Event Broadcasting, and more a breeze!
ApiEndpoints - A project for supporting API Endpoints in ASP.NET Core web applications.
Kafka Client
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
FluentScheduler - Automated job scheduler with fluent interface for the .NET platform.