FastEndpoints
Carter
Our great sponsors
| FastEndpoints | Carter | |
|---|---|---|
| 15 | 15 | |
| 3,904 | 1,977 | |
| 6.4% | 2.6% | |
| 9.7 | 4.5 | |
| 4 days ago | 5 months 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/
Carter
-
Explorando o Carter: Um Framework Simples e Eficaz para APIs em .NET
Para saber mais: Carter Github
-
17 Amazing Community Packages for .NET Developers
And what about Carter for minimal APIs?
- Does an open source 'backend platform' exist for dotnet?
-
What is the dotnet equivalent to Python's Flask?
Nancy became Carter https://github.com/CarterCommunity/Carter
-
Reprise - a micro-framework that brings the REPR pattern into Minimal APIs
The results for Carter were a surprise for me as well and I even reported that: https://github.com/CarterCommunity/Carter/issues/315
-
Does anyone like minimal API?
Check out Carter if you're a Nancy fan =)
-
is injecting a iserviceprovider instance considered a anti-pattern
As a good example on how to build over base asp.net core there's project Carter who provides a nice module experience.
-
FastEndpoints alternatives - ApiEndpoints and Carter
3 projects | 20 Jan 2022
- ASP.NET Core 6: Autenticación JWT y Identity Core
-
As a .Net/NodeJS developer, this video helped me reconcile some Minimal API patterns
I would recommend Carter. I just started playing with it and It’s been delightful so far. https://github.com/CarterCommunity/Carter
What are some alternatives?
ApiEndpoints - A project for supporting API Endpoints in ASP.NET Core web applications.
SoapCore - SOAP extension for ASP.NET Core
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.
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
SqlClient - Microsoft.Data.SqlClient provides database connectivity to SQL Server for .NET applications.
FastEndpoints - A light-weight REST API development framework for ASP.Net 6 and newer. [Moved to: https://github.com/FastEndpoints/Library]
RestSharp - Simple REST and HTTP API Client for .NET
ASP.NET MVC Boilerplate - .NET project templates with batteries included, providing the minimum amount of code required to get you going faster.
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
MinimalApiPlayground - A place I'm trying out the new ASP.NET Core minimal APIs features.
Flurl.Http - Fluent URL builder and testable HTTP client for .NET
MiniValidation - A minimalist validation library for .NET built atop the existing features in `System.ComponentModel.DataAnnotations` namespace