Goodbye controllers, hello Minimal APIs
summary
Minimal APIs use C# 9/10 features like top-level statements and implicit usings plus inferred lambda types and attributes on lambdas to remove MVC boilerplate. A working REST CRUD for Customers is built with minimal APIs, Swagger docs, DI, FluentValidation and the third‑party FastEndpoints library, and it performs faster than controllers. Recommended for demos, POCs and microservices (services under ~1,500 lines); not ideal for very large enterprise monoliths. Microsoft predicts 40–80% of new use cases may adopt them.
AI-written summary · about
chapters (10)
- 0:00Start
- 7:51Top-level statements
- 9:26Implicit using statements
- 10:39Inferred lambda types
- 25:06Unsupported features
- 27:37Program.cs hell
- 30:30Controllers for APIs are weird
- 47:56Minimal Valley
- 49:58How people get into a programming language
- 52:33The programming language express
related talks
46mLet’s Get Minimal: .NET 6 New APIs in ASP.NET Core
54mMinimal APIs in ASP.NET 6.0
58mMinimal APIs in ASP NET 6 0
49mAn Opinionated, Maintainable REST API Architecture for ASP.NET Core
01h 01mMinimal API +SPA, a perfect match
01h 01mNever RESTing – RESTful API Best Practices using ASP.NET Web API
42mASP .NET Basics for Experts
59mASP .NET Basics for Experts
