#Asp-Net-Core
7 notas · última:
HTTP Best Practices Using ASP.NET Core And Polly
The page explains HTTP resiliency in ASP.NET Core with Polly, focusing on transient errors. It shows retry, circuit breaker, and bulkhead policies and how they are combined with HttpClientFactory.
API Versioning in ASP.NET Core
The page explains how API versioning lets ASP.NET Core APIs evolve without breaking existing clients, and shows how to add it with Asp.Versioning, choose version readers, and manage controllers and Minimal APIs.
Logging Best Practices in ASP.NET Core
The post recommends Serilog for ASP.NET Core, using the right log levels, filters, structured logging, sensitive-data protection, error logging, log rotation, async sinks, and a centralized UI like Seq.
How to Implement Response Caching for Improved Performance?
Response caching stores API or web app responses in a cache so later requests can reuse them faster. The post lists benefits, request types, constraints, real-world uses, and a simple Postman test.
The dangers and gotchas of using scoped services in IConfigureOptions
The post explains how ASP.NET Core options work, why `IOptions<>` and `IOptionsSnapshot<>` differ, and how scoped services can create captive dependencies when used in `IConfigureOptions<>`.
Web Service Integrations Using Hangfire in ASP.NET Core
The post shows how to split an incoming and outgoing web service integration into synchronous validation and async Hangfire jobs, so RPC work becomes retryable, durable, and non-blocking.
API Versioning In ASP.NET Core
The article explains why API versioning matters in ASP.NET Core Web API and shows three approaches to route requests by version: query string, URL, and HTTP header.