Database Performance from the API Layer
API performance is frequently limited by database access.
Avoid N+1 queries. Select only required fields when possible. Create appropriate indexes. Use pagination. Analyze query plans. Limit expensive joins or aggregations. Cache suitable read-heavy data.
Never solve a database bottleneck by simply increasing the API timeout. A slow query multiplied across hundreds of concurrent requests can exhaust the database connection pool and cause cascading failure.
Beware N+1 Queries
Fetching one collection and then issuing one database query for every returned item can turn a single API request into hundreds of database operations.