Backend

.NET

Microsoft's cross-platform platform for C#, with ASP.NET Core for web and APIs.

What it is

Modern .NET (called .NET Core until 2020) is open and runs on Windows, Linux and macOS. It includes the CLR runtime, a large standard library and the C# compiler.

ASP.NET Core builds web apps and APIs: minimal APIs, MVC, Blazor, SignalR for real time. Entity Framework Core handles data access.

The platform is known for high performance and strong tooling (Visual Studio, Rider). New releases ship every year, with LTS versions supported for several years.

Use it when

  • Enterprise backends and integrations in the Microsoft and Azure ecosystem.
  • You need high performance and strict typing.
  • One stack for web, desktop and games (Unity uses C#).

Avoid it when

  • The team does not use C# and will not learn it.
  • A tiny script or simple automation: lighter languages are quicker to build in.

Key concepts

CLR
The runtime with JIT compilation and a garbage collector.
ASP.NET Core
The web framework with a middleware pipeline and built-in DI.
EF Core
An ORM with migrations and LINQ queries.
NuGet
The .NET package manager.

Example

A minimal API with a route and a parameter.

Interview questions

  1. 1. How does .NET Core differ from .NET Framework?

    .NET Framework runs only on Windows and is no longer actively developed. Modern .NET is cross-platform, open and faster.

  2. 2. What is the middleware pipeline in ASP.NET Core?

    A sequence of components a request passes through: auth, routing, error handling. The registration order matters.

  3. 3. Why async/await?

    To avoid blocking threads during I/O. The method returns a Task, and the thread is free while the operation waits.

Logos belong to their owners and are used for identification only. Icons: Simple Icons (CC0), Devicon (MIT).