3 ms·

There's also Fast Endpoints[1], which Kind of the best of both worlds, minimal-API and REPR. 1: https://fast-endpoints.com/ https://fast-endpoints.com/

• tracker1 1y ago
  Came to mention the same... really like FastEndpoints myself a lot.
  • pier25 1y ago
    Same although Minimal APIs are slowly getting there. In dotnet 10 we will finally get validation.
    • tracker1 1y ago
      Fair enough... I'd probably stick to Minimal APIs if there were fewer than 5-10 routes in a smaller service. But, with the startup and runtime overhead of .Net, I'm inclined to prefer more monolithic approaches for most general use. Just without weighing it down with a lot of heavy handed enterprisey abstractions. Edit: Of course, Aspire definitely looks interesting for more complex needs.
      • pier25 1y ago
        AFAIK FastEndpoints uses Minimal APIs... so wouldn't the overhead be similar?
        • tracker1 1y ago
          They do, and it's not so much about the overhead in terms of performance so much as the cognitive load of spreading out what would otherwise be a smaller/simpler codebase.
• prodbro 1y ago
  > There's also Fast Endpoints[1] thank for the pointer ! The syntax seems cool and comprehensive, i like it. I made some test and like its name, it is very fast : performances are closed to SimpleW, just a little bellow. But its memory footprint is the half, so i'm impressed. I will check the code, sure there are interesting things into.