Loading content
ASP.NET Core is a modular, cross-platform web framework from Microsoft for building web APIs, MVC applications and real-time services. It delivers high performance, an integrated middleware pipeline and flexible hosting options (Kestrel, IIS, containers, cloud). Typical uses range from microservices to monolithic web apps.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Technical building block: can be automated, integrated, or operated.
Concrete cog in the system that works inside larger relationships.
ASP.NET Core is a modular, cross-platform web framework from Microsoft for APIs, MVC applications, and real-time services.
ASP.NET Core originated at Microsoft as a redesign of ASP.NET to bring the previously separate MVC and Web API stacks into one modular framework and make it cross-platform. The project was first called ASP.NET vNext and then ASP.NET 5; at the 1.0 release in 2016 it was renamed ASP.NET Core. It is developed openly with the .NET Foundation and the community.
Think of ASP.NET Core as three layers: at the bottom, a host starts the application on Kestrel, IIS, or inside a container. In the middle, each HTTP request passes through a middleware chain, where components can inspect, enrich, or end it. At the top, MVC, Razor Pages, Minimal APIs, SignalR, or Blazor implement the web logic and rely on .NET and dependency injection.
ASP.NET Core runs on .NET and uses its runtime, type system, and tooling.
Each request moves through components in sequence that inspect, change, or forward it.
Kestrel, IIS, containers, and cloud hosts determine how the application starts and is reached.
APIs, MVC, Razor Pages, SignalR, and Blazor cover different web tasks on the same platform.
Services are provided through a container instead of being hard-wired into components.
ASP.NET Core fits when teams want to run APIs, MVC front ends, or real-time features on Windows, Linux, or in containers while performance and flexible hosting matter. It works well for microservices and for larger web applications. The trade-offs are the dependency on .NET, the choice among several app models, and migration effort from ASP.NET 4.x or other legacy stacks.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.