ApiEndpoints
FastEndpoints
Our great sponsors
ApiEndpoints | FastEndpoints | |
---|---|---|
22 | 15 | |
2,985 | 3,904 | |
- | 6.4% | |
4.3 | 9.7 | |
about 1 month ago | 3 days 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.
ApiEndpoints
- Web apis with controllers but whats the other way
-
Does anyone like minimal API?
I personally prefer the API Endponts project that doesn’t get the love it deserves. It’s really the best of both worlds. It breaks each endpoint up into one file to make it easier to manage and prevents ginormous Controllers.
-
Are minimal APIs meant to be used for lightweight projects or do they offer something controllers don't?
I personally think it feels "cleaner" when using the controllers instead because they provide more out of the box features. Having one endpoint per file is a nice thing so I'm thinking about using the ApiEndpoints ( https://github.com/ardalis/ApiEndpoints ) package.
-
Need help for refactoring my Controller
You can follow a "controller per endpoint" strategy. One good way to do it is with Steve Smith ApiEndpoints: https://github.com/ardalis/ApiEndpoints
- Need help understanding the purpose of MediatR in vertical slices architecture.
-
Thick or thin API controllers?
I'm not disputing the benefits of thin controllers but there are other ways to make the controllers thinner. For example, I could use libraries such as ApiEndpoints which allows me to have one handler class per REST endpoint. Basically, MediatR pattern but at the ASP.net level.
The only think I would suggest is to break endpoints into separate files via smth like this https://github.com/ardalis/ApiEndpoints
-
FastEndpoints v3.0 released with easy api versioning support!
You really should compare against https://github.com/ardalis/ApiEndpoints
-
FastEndpoints alternatives - ApiEndpoints and Carter
3 projects | 20 Jan 2022
- ASP.NET Core 6: Autenticación JWT y Identity Core
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/
What are some alternatives?
FastEndpoints - A light-weight REST API development framework for ASP.Net 6 and newer. [Moved to: https://github.com/FastEndpoints/Library]
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.
MediatR - Simple, unambitious mediator implementation in .NET
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.
IdentityServer4 - OpenID Connect and OAuth 2.0 Framework for ASP.NET Core
SqlClient - Microsoft.Data.SqlClient provides database connectivity to SQL Server for .NET applications.
RestSharp - Simple REST and HTTP API Client for .NET
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
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
AutoMapper - A convention-based object-object mapper in .NET.
Flurl.Http - Fluent URL builder and testable HTTP client for .NET