PPhying中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Avoiding N+1 Database Queries in ASP.NET: A Practical Guide

hackerone.com | blog | #performance | #database | #orm | #aspnet | #dotnet | #entity-framework
📄 Raw .md⬇️ Download .md🔗 Original ↗

Summary

The N+1 query problem in ASP.NET's Entity Framework issues a query per related record, degrading performance at scale; eager loading with Include, projections, batch queries, and AsNoTracking fix it.
Published
Collected

Related coverage

blog · hackerone.com
What To Look For When Reviewing C#
PullRequest reviewer Artak Mkrtchyan flags common server-side C# issues, starting with unnecessary allocations that bloat the heap and trigger costly garbage collection in ASP.NET services.
research · blog.quarkslab.com
MongoDB vs. Elasticsearch: The Quest of the Holy Performances
A practical MongoDB vs. Elasticsearch comparison for Ivy, Quarkslab's large-scale network reconnaissance tool: storing and mining unstructured data on ordinary hardware, and the trade-offs involved.
blog · hackerone.com
Unlocking Performance with Memoization: A Developer's Guide
HackerOne's developer guide to memoization: caching expensive function results for reuse, Python's functools.lru_cache, when the technique applies (limited inputs, costly calls, repeated arguments) and its use beyond individual functions.
blog · hackerone.com
The Role of ORMs in Modern Web Frameworks
ORMs bridge object-oriented code and relational databases, automating CRUD and reducing SQL injection risk; a tour of Django ORM, ActiveRecord, Entity Framework, and TypeORM trade-offs.
blog · hackerone.com
Embracing Dependency Injection in ASP.NET for Loose Coupling and Testability
HackerOne's guide to dependency injection in ASP.NET explains how IoC containers delegate dependency creation, promoting loose coupling, maintainability, and testability in .NET applications.
blog · hackerone.com
Leveraging Async/Await in ASP.NET for Enhanced Performance
Covers effective async/await usage in ASP.NET: reserve it for I/O-bound work, avoid .Result and .Wait() deadlocks with ConfigureAwait(false), and skip async for CPU-bound paths.
Back