Advantages and disadvantages of FastEndpoints

This page summarizes the projects mentioned and recommended in the original post on /r/dotnet

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • clean-minimal-api

    A project showcasing how you can build a clean Minimal API using FastEndpoints

  • then how about not muddying up your controller/handler with a million attributes for swagger documentation? here's a sample swagger documentation class from nick-chapsas. they can stay away from your handler keeping them lean.

  • safe-routing

    A C# source generator for ASP.NET Core razor pages and MVC controllers which produces strongly-typed identifiers for routes.

  • There are other approaches to safe routing, like those that use C# Source Generators

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
  • Result

    A result abstraction that can be mapped to HTTP response codes if needed. (by ardalis)

  • Using the Nuget Package Ardalis.Result for mapping result objects to HTTP Response Codes and associated objects; FastEndpoint has its own way of approaching this problem, which seems to be to hang everything off an "Endpoint" and optionally using Swagger to redundantly describe the route's behavior; this seems like a step backwards from more advanced Web frameworks in other languages. The advantage of Ardalis.Result should be clear - each closed form of Ardalis.Result can have its own knowledge of what it does, and therefore automatically describe the abstract transformations it does on a request. In functional programming, this "abstract transformation" is typically called a monad transformer or Arrow. Once you have a type that describes the abstract transformation, plugging that into Swagger should be straight-forward.

  • Swashbuckle.AspNetCore

    Swagger tools for documenting API's built on ASP.NET Core

  • It isn't where it needs to be. Notably, it cannot out-of-the-box handle open generic data types. There's also plenty of issues logged for this library. - Personally, that makes me think the approach is overly complicated and doesn't do its job as well as it should.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts