Northwind Traders is a sample application built using ASP.NET Core and Entity Framework Core. The architecture and design of the project is explained in the video:

Generate ASP.NET Core WebAPI model with Entity Framework Core Generator 

request per second got increased significantly to 3742 which is approximate ~50% increase. 

ASP.NET Core: Saturating 10GbE at 7+ million request/s

In these “platform” comparisons that’s:
- x1.78 faster than ngnix
- x2.93 faster than Java’s Servlet (x7.76 faster than Servlet on Tomcat)
- x7.36 faster than Golang’s “net/http” package
- x8.06 faster than node.js running as a cluster of 28 processes (as node.js is single threaded)
 

In this section, I’m going to cover how you can use SignalR outside of a Hub. In most asp.net core applications, you will likely want to communicate with the connect clients from within your application but outside of a Hub. You can accomplish this by using the HubContext.

For example, an ASP.NET Core MVC Controller or any other class that is instantiated by ASP.NET Core’s Dependency Injection.

The HubContext allows you to send messages to your connected clients. It has many of the same features to communicate with clients as when you are inside of a Hub.  

Project Bedrock

Project bedrock is about further decoupling the components of Kestrel so that we can use it as the foundation for our non-http networking stack. 

Here's the list of what's new in this preview:

• Razor Components
• SignalR client-to-server streaming
• Pipes on HttpContext
• Generic host in templates
• Endpoint routing updates