MicroBenchmarksDotNet
ApiEndpoints
Our great sponsors
| MicroBenchmarksDotNet | ApiEndpoints | |
|---|---|---|
| 2 | 22 | |
| 5 | 2,985 | |
| - | - | |
| 5.5 | 4.3 | |
| 2 months ago | about 1 month ago | |
| C# | C# | |
| - | 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.
MicroBenchmarksDotNet
-
Why are UDP sockets faster in Windows safe mode?
I don't think that is the case. I attached all my benchmark results in the relase section: https://github.com/JohannesDeml/MicroBenchmarksDotNet/releases/tag/1.0.0
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
What are some alternatives?
NetFabric.Hyperlinq - High performance LINQ implementation with minimal heap allocations. Supports enumerables, async enumerables, arrays and Span<T>.
FastEndpoints - A light-weight REST API development framework for ASP.NET 6 and newer.
Unchase.FluentPerformanceMeter - :hammer: Make the exact performance measurements of the public methods for public classes using this NuGet Package with fluent interface. Requires .Net Standard 2.0+. It is an Open Source project under Apache-2.0 License.
FastEndpoints - A light-weight REST API development framework for ASP.Net 6 and newer. [Moved to: https://github.com/FastEndpoints/Library]
ASP.NET Boilerplate - ASP.NET Boilerplate - Web Application Framework
MediatR - Simple, unambitious mediator implementation in .NET
BenchmarkDotNet - Powerful .NET library for benchmarking
IdentityServer4 - OpenID Connect and OAuth 2.0 Framework for ASP.NET Core
Ryujinx - Experimental Nintendo Switch Emulator written in C#
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.
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
AutoMapper - A convention-based object-object mapper in .NET.