The next 5 years of ASP.NET Core
summary
Project Bedrock is an extensible networking API that splits transport and protocol so Kestrel swaps libuv for .NET sockets and SignalR can run over raw TCP instead of WebSockets, enabling HTTP/3/QUIC and named pipes. Endpoint routing unifies MVC, SignalR and gRPC and a “route to code” prototype shows single-file minimal apps in one source file. Publish experiments use crossgen and the linker to shrink self‑contained apps from ~92MB to 74MB conservative and to 25–28MB best case, with startup gains of ~30–100ms.
AI-written summary · about
chapters (43)
- 0:00Intro
- 0:17Ryan Nowak
- 0:45New Ideas
- 1:22Roadmap
- 2:10Project Bedrock
- 4:00Server Architecture
- 6:43HTTP to HTTPS
- 7:44Transports protocols
- 8:09Bedrock
- 10:17Signal R
- 10:39Chat Demo
- 12:44Why should you care
- 14:33The future of Project bedrock
- 15:48Project Houdini
- 16:09Platform vs MVC
- 16:38Adding more frameworks
- 17:38New routing system
- 19:05Layering diagram
- 19:33Houdini
- 20:52Controllers
- 22:41Solutions
- 23:24Declarative vs Rich
- 25:36Route to Code
- 26:40Demo
- 26:52New way of speed
- 27:27One class one file
- 32:22The future
- 33:03Publishing
- 34:00File Size
- 37:08Single File Host
- 38:22Startup Performance
- 41:34Linker
- 42:28Tree Shaking
- 43:33Challenges
- 46:06Solutions to Challenges
- 47:20Size Results
- 49:16Screenshot
- 49:45Performance results
- 52:11Glaser
- 52:37Electron
- 53:44Notification
- 55:44Export Data
- 59:09Blazer Process
related talks
01h 01mASP.NET Core 3.0: State of the art
01h 02mIntroducing ASP.NET Core Sockets
01h 15mWhat's Next for ASP.NET Core & Blazor
51mThe State of .NET (vol. 1)
01h 05mWhat does an Open Source Microsoft Web Framework Look Like
01h 01mWhat's New In ASP.NET Core
01h 00mWhat's New in ASP.NET Core?
46mASP.NET Core and Blazor futures Q&A