FastEndpoints
MediatR
Our great sponsors
FastEndpoints | MediatR | |
---|---|---|
15 | 53 | |
3,904 | 10,614 | |
6.4% | - | |
9.7 | 6.2 | |
4 days ago | 11 days ago | |
C# | C# | |
MIT License | Apache License 2.0 |
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.
FastEndpoints
-
Choosing Between Controllers and Minimal API for .NET APIs
Bonus Time! In addition to the Microsoft-supported methods above, many community frameworks exist for building APIs with .NET. FastEndpoints is an option I found recently that seems very promising. With performance benchmarks that put them on par with Minimal API, they are firmly ahead of Controller-based APIs.
-
How do you structure large Minimal API Projects?
Have you had a look at FastEndpoints yet? Any thoughts?
-
Microsoft launches new app store for Windows – from React to Shoelace, Lit, Vite
And yet, all Microsoft's demos for the upcoming changes for Blazor in .NET 8 (like SSR) has been a public facing recipe site (e.g. https://www.youtube.com/watch?v=QD2-DwuOfKM). I'd say this is a very similar use case as the Microsoft Store.
I love .NET and ASP.NET Core, but I use it purely for backend. And even there, I use 3rd party libraries like Fast Endpoints (https://fast-endpoints.com/). Microsoft keeps bringing in new technologies and effectively abandoning the ones that fall out of favour (look at the progression from MVC -> Razor Pages -> Blazor). I do not blame the Microsoft Store team for not trusting the .NET team to not simply abandon Blazor as well somewhere down the line and instead opt for other technologies for the front-end.
-
Idea validation | low-code API factory
I also find a very similar framework in .NET "Fast Endpoints"
-
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.
- Should I utilize C#/.NET Core, or go with Typescript for a React front end?
-
Which 'part' of dotnet should I learn for backend web dev?
Ive personally been using FastEndpoints which is a community built thing on top of minimal apis - https://fast-endpoints.com/
-
Reprise - a micro-framework that brings the REPR pattern into Minimal APIs
I've just started to use a similar thing, and it's so much better than controllers - https://fast-endpoints.com/
-
Easiest/Standard way to implement a simple HTTP REST API?
Sort of minimal but check out FastEndpoint. https://fast-endpoints.com/
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.
What are some alternatives?
ApiEndpoints - A project for supporting API Endpoints in ASP.NET Core web applications.
Mediator.Net - A simple mediator for .Net for sending command, publishing event and request response with pipelines supported
Carter - Carter is framework that is a thin layer of extension methods and functionality over ASP.NET Core allowing code to be more explicit and most importantly more enjoyable.
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
Refit - The automatic type-safe REST library for .NET Core, Xamarin and .NET. Heavily inspired by Square's Retrofit library, Refit turns your REST API into a live interface.
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+.
SqlClient - Microsoft.Data.SqlClient provides database connectivity to SQL Server for .NET applications.
Brighter - A framework for building messaging apps with .NET and C#.
RestSharp - Simple REST and HTTP API Client for .NET
NetCoreServer - Ultra fast and low latency asynchronous socket server & client C# .NET Core library with support TCP, SSL, UDP, HTTP, HTTPS, WebSocket protocols and 10K connections problem solution
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.