things you should know about .Net core

Microsoft rebranded ".NET Core" to just ".NET" starting with version 5.0 to signify that it is the single, unified platform moving forward, completely replacing the legacy, Windows-only .NET Framework. Whether you are building web APIs, cloud-native microservices, or mobile apps, here is a breakdown of the critical architecture, patterns, and features you should know about modern .NET.

Core Architecture & Environment

• True Cross-Platform Performance: You can build, compile, and run your applications on Windows, macOS, and Linux.
• Kestrel Web Server: The platform utilizes Kestrel, a lightweight, high-performance HTTP server designed to handle raw internet traffic or sit behind a reverse proxy like Nginx or IIS.
• Modular Pipeline Architecture: It uses a flexible middleware pipeline to handle HTTP requests sequentially, enabling you to add or remove features easily.
• Flexible Deployment Models: You can deploy apps as Framework-Dependent (small files that rely on a shared machine runtime) or Self-Contained (larger packages containing the complete runtime environment).
• Docker Container Support: The lightweight footprint of the framework makes it highly optimized for microservices and continuous deployment in Docker containers.

Fundamental Development Patterns

• Built-in Dependency Injection (DI): You do not need third-party tools anymore; the platform includes native DI containers that manage component lifecycles using Transient, Scoped, or Singleton registration lifetimes.
• Asynchronous-First Approach: High request concurrency relies heavily on proper implementation of async/await patterns; breaking asynchronous chains with .Result or .Wait() risks locking production threads.
• Unified Web Frameworks: Legacy systems separated MVC (web pages) and Web API (REST endpoints) pipelines, but modern versions share the exact same controller routing logic.
• Minimal APIs: For rapid prototyping or small services, you can drop heavy controller classes completely and map endpoints fluently inside a single entry file.

Integrated Ecosystem Utilities

• Entity Framework Core (EF Core): The primary Object-Relational Mapper translates your C# code directly into SQL schemas via CLI database migrations.
• Blazor for Frontend: You can write client-side interactive web user interfaces inside components using HTML and C# instead of dealing with JavaScript dependencies.
• HybridCache Defaults: Modern applications prioritize HybridCache setups out-of-the-box to unify in-memory caching speeds with persistent Redis storage layers.