Performance

TL;DR Repeating logic across controllers (like logging or header checks)? Move it to middleware. Modifying requests/responses in controllers? Middleware handles that cleanly and early. Your services use HttpContext? Extract that logic into middleware for cleaner, testable code. If your services are bloated or you’re duplicating logic across controllers, middleware might be the extension point you actually need. Many developers reach for filters or services first, when middleware would’ve been faster, simpler, and more maintainable. ...

Async/await is powerful but overused. This guide breaks down async misconceptions, shows real enterprise use cases, and gives you a practical decision framework for async in C#.

Master IEquatable in C# to optimize equality checks, improve collection performance, and eliminate boxing overhead. Essential for value types and collections.

Discover when it’s justified to break SOLID principles for performance in C#. Learn how to measure, isolate, and document exceptions, see real-world trade-offs, and keep your codebase maintainable, even in the engine bay of high-throughput systems.

Discover why structs as dictionary keys can cause hidden allocations in C#. Learn how to implement IEquatable, use readonly and record structs, and write allocation-free, high-performance code for hot paths.

TL;DR Middleware order in ASP.NET Core directly affects authentication, CORS, routing, and logging. Register exception handling, HTTPS redirection, and logging middleware early in the pipeline. Place CORS before authentication and routing to avoid preflight and header issues. Authentication must come before authorization and routing for secure endpoints. Use tools like MiddlewareAnalysis and custom logging middleware to debug pipeline flow. Common mistakes include routing before authentication, CORS after auth, and late exception handling. Correct middleware order prevents security holes, debugging nightmares, and production outages. The Hidden Culprit Behind Mysterious Pipeline Failures Picture this: your ASP.NET Core API works perfectly in development, but authentication randomly fails in production. CORS headers appear inconsistently. Some endpoints return 404s that should work. The logs show everything should be working correctly. ...

TL;DR: Efficient C# File Processing Strategies Prevent system crashes: Avoid naive parallel processing that launches thousands of concurrent file operations. Optimize throughput: Use SemaphoreSlim to control concurrency (start with 2x CPU cores) for balanced performance. Reduce memory consumption: Implement true async I/O with useAsync: true and process files line-by-line instead of loading them entirely. Minimize database overhead: Batch related records from multiple files before making database calls. Maximize system resources: For production systems, implement adaptive throttling that responds to CPU/memory conditions. Leverage modern C# features: Use IAsyncEnumerable for efficient streaming and TPL Dataflow for complex processing pipelines. Ever tried to build an import tool that needs to process thousands of CSV files at once? I have, and I learned the hard way that simply starting a thousand file operations simultaneously is a recipe for disaster. ...

TL;DR - Practical Tips for ASP.NET Core HTTP Logging Middleware Use EnableBuffering() to safely log request bodies and reset stream position after reading. Capture response bodies by swapping HttpResponse.Body with a MemoryStream and restoring after logging. Always filter or redact sensitive data before logging HTTP bodies. Set size limits and skip large or binary payloads to avoid performance issues. Filter logs by endpoint, HTTP method, or custom attributes for clarity. Built-in HttpLogging is simple; custom middleware offers full control and advanced filtering. Use structured logging and external services for production monitoring. Wrap middleware in extension methods for clean, configurable registration. Leverage PipeReader and System.IO.Pipelines for more efficient memory usage. Use Span<T> and ArrayPool<T> for zero-allocation processing of large payloads. Consider implementing request sampling in production to reduce log volume. Use a complete middleware implementation that combines all best practices. 1. How does EnableBuffering help you log request bodies in ASP.NET Core? EnableBuffering allows you to read request bodies multiple times without breaking the pipeline. ...

TL;DR: Angular’s @defer directive delays non-critical UI rendering, cutting initial load time by up to 97% in real apps. Use it to lazy load heavy components, reduce Time to Interactive (TTI), and improve Core Web Vitals. Includes real benchmarks and production-ready examples. Introduction Ever loaded up an Angular app and watched that progress bar crawl while your users bail? Yeah, me too. That’s why I got so excited when the Angular team released the @defer feature. It’s a game-changer for those of us battling slow initial load times. ...

Ever used the params keyword in C#? If you write C# code regularly, you probably reach for it whenever you need to pass a variable number of arguments to a method. It’s super handy, letting you skip the tedious step of creating arrays first. But until now, there’s been a limitation: params only worked with arrays. This meant every call created memory allocations with potential performance costs. The good news? C# 14 is changing the game by extending params to work with modern collections like IEnumerable<T>, Span<T>, and more. ...