ASP.NET Core Futures Roadmap
summary
Roadmap focuses on concrete runtime and library changes: Kestrel becomes transport‑pluggable with a new sockets transport (moving off libuv) and a pipeline‑based I/O layer, SignalR and higher‑level messaging run on a new socket abstraction, and HTTP/3 via QUIC (HTTP/3) is targeted. Performance work adds pipelines, Span APIs and UTF‑8‑oriented encoders to cut allocations; initial pipeline integration drops throughput ~50% then recovers to parity after optimizations. Demos show prototypes (some flaky) for native compilation and client/server libraries.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:07Performance and database stack
- 3:54Cortex Lab and BCL innovations
- 7:05Span and memory optimizations
- 8:09Kestrel transport layer
- 10:35Efficient pipelines
- 16:13Kestrel migration results
- 22:10Cortex Lab demos
- 28:15Custom HTTP client
- 32:50QUIC protocol
- 40:50Native compilation
- 44:37SignalR improvements
- 47:04Socket abstraction
- 54:08Generic host libraries
- 56:40Health checks
- 57:46RESTful APIs
- 59:32Simplified MVC
- 1:01:03TypeScript and Blazor
- 1:02:24Conclusion and Q&A
related talks
30mNode.js: What's Next?
50mNodeJS Future
01h 01mThe State of Node Core
56mReal-Time, Distributed Applications w/ Akka.NET, Kubernetes, .NET Core, and Azure Kubernetes Service
21mA QUIC Update
23msocket.io
46mStreaming three ways with Blazor: REST, gRPC, and SignalR
24mWeb APIs in Node.js Core: Past, Present, and Future
