FastEndpoints
awesome-software-architecture
Our great sponsors
| FastEndpoints | awesome-software-architecture | |
|---|---|---|
| 15 | 71 | |
| 3,904 | 7,680 | |
| 6.4% | - | |
| 9.7 | 8.9 | |
| 4 days ago | about 2 years ago | |
| C# | C# | |
| MIT License | Creative Commons Zero v1.0 Universal |
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/
awesome-software-architecture
-
Awesome Software Architecture
Repository: https://github.com/mehdihadeli/awesome-software-architecture
- What books do you guys recommend getting into designing software architecture?
- A curated list of articles, videos, and other resources to learn and practice software architecture and its patterns
- A curated list of articles, videos for learning software architecture patterns
- A curated list of articles, and videos for learning software architecture, patterns
- A curated list of articles, videos, and other resources to learn and practice software architecture, and patterns.
- A curated list of articles, videos, and other resources to learn and practice software architecture, patterns, and principles
- List of articles, videos, and other resources to learn and practice software architecture, patterns, and principles
- A curated list of articles, videos, and other resources to learn and practice software architecture, patterns, and principles.
What are some alternatives?
ApiEndpoints - A project for supporting API Endpoints in ASP.NET Core web applications.
turborepo - Incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust – including Turborepo and Turbopack. [Moved to: https://github.com/vercel/turbo]
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.
awesome-system-design - A curated list of awesome System Design (A.K.A. Distributed Systems) resources.
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.
Towel - Throw in the towel.
SqlClient - Microsoft.Data.SqlClient provides database connectivity to SQL Server for .NET applications.
C# Algorithms - :books: :chart_with_upwards_trend: Plug-and-play class-library project of standard Data Structures and Algorithms in C#
RestSharp - Simple REST and HTTP API Client for .NET
Algorithmia - Algorithm and data-structure library for .NET 4.5.2+/Netstandard 2.0+. Algorithmia contains sophisticated algorithms and data-structures like graphs, priority queues, command, undo-redo and more.
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
FastEndpoints - A light-weight REST API development framework for ASP.Net 6 and newer. [Moved to: https://github.com/FastEndpoints/Library]