Cache GET responses only when user context is clear
Do not cache a GET response unless the cache key matches the user, tenant, and permission boundary that shaped it.
Aspnet-Core
Middleware order is important
Place ASP.NET Core middleware in the order that matches routing, security, and endpoint behavior.
Pass CancellationToken through real boundaries
Thread cancellation through every expensive operation instead of dropping it mid-chain.
Prefer health checks that test dependencies deliberately
Health checks should say something useful about readiness without turning every probe into production load.
Use HybridCache when cache stampedes matter
Use HybridCache for expensive shared lookups where many callers can miss at once.
Use ProblemDetails as your API error contract
Return one predictable error shape instead of inventing a new JSON format for every failure.