FastEndpoints
FastEndpoints
Our great sponsors
FastEndpoints | FastEndpoints | |
---|---|---|
15 | 16 | |
3,904 | 1,936 | |
6.4% | - | |
9.7 | 9.9 | |
4 days ago | over 1 year ago | |
C# | C# | |
MIT License | 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.
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/
FastEndpoints
- FastEndpoints has reached v5.0 after 1 year of development [107k downloads / 1.9k gh stars / 1.1k commits]
- FastEndpoints – API Framework for Asp.net Using the REPR Pattern
- FastEndpoints template
-
is injecting a iserviceprovider instance considered a anti-pattern
In a recent podcast episode I recorded with Nick Chapsas, we discussed both Minimal API and Mediatr (due to be published on the 1st April). He mentioned a library I hadn't heard of before called Fast Endpoints, which is yet another option. So many different ways to skin a cat. I haven't used Carter, but did use Nancy back in the day.
-
6 .NET Myths Dispelled — Celebrating 21 Years of .NET
There's also Fast Endpoints as another way of doing a similar concept (This has API design issues imo, but the concept is solid). It ends up being similar to how a lot of people use MediatR, it's just instead of using controllers you use MapXXX to call MediatR. This just allows people to cut out the MVC overhead.
-
We Need to Have a Talk About MediatR
i believe i've built such a thing. or at least something close to that ;-)
- FastEndpoints v3.0 released with easy api versioning support!
-
FastEndpoints alternatives - ApiEndpoints and Carter
3 projects | 20 Jan 2022
-
Awesome Software Architecture: A curated list of useful resources about software architecture and design principles.
awesome! page looks a bit empty. maybe my rest api framework belongs there too as it's an implementation of REPR pattern https://github.com/dj-nitehawk/FastEndpoints
-
Is minimal api the way to go now?
that's why integration/functional testing with WebApplicationFactory is the way to go.
What are some alternatives?
ApiEndpoints - A project for supporting API Endpoints in ASP.NET Core web applications.
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.
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.
RestSharp - Simple REST and HTTP API Client for .NET
SqlClient - Microsoft.Data.SqlClient provides database connectivity to SQL Server for .NET applications.
Ocelot - .NET API Gateway
Simple.OData.Client
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