HTTP/3 is more than just a protocol specification to keep an eye on. Thru QUIC, ASP.NET Core Kestrel supports HTTP/3, and Microsoft is refining its implementation. Compared to earlier HTTP versions, HTTP/3 offers separate streams, uses QUIC rather than TCP, and can lower connection-establishment time. However, the crucial query for API developers is not: Is…
Author: Pablo Francesco
Using Modern.NET’s Integrated Rate Limiting and Output Caching
Third-party middleware packages are no longer necessary thanks to native performance features included in modern.NET: While output caching significantly lowers database load by storing whole HTTP replies server-side, rate limitation shields your APIs against misuse and denial-of-service attacks. Step 1: Configuring Built-In Rate Limiting Rate limiting controls the frequency of requests clients can make to…
Best Practices for Authentication and Authorization in ASP.NET Core 10
One of the most important components of any online application is security. Protecting user identities, sensitive company data, and APIs becomes more crucial as apps develop. Even though ASP.NET Core offers a strong foundation for authorization and authentication, incorrect implementation can expose apps to security threats and illegal access. With its configurable authentication schemes, policy-based…
You Don’t Need to Create All Properties Inside a DTO to Successfully Deserialize
The example below might seem like very simple advice, but I found people across many codebases do not know this. This, in turn, leads to excessive usage of the JsonNode class, forcing developers to lose the benefits of compiler support in a strongly typed language. Example JSON Consider the JSON below: string json = “””…
Minimal APIs vs Controllers: The .NET Debate That Just Won’t Die
Picture this. It’s Monday morning, and your team lead drops a message in the group chat: “New service starting today. Minimal API or Controller?” A few seconds of silence follow. Then everyone starts typing at once. Even years after Minimal APIs were introduced, this question continues to divide .NET teams. Some developers prefer the simplicity…