REST API – N+1 Problem

Last Updated :

1. N+1 Problem

N+1 problem is mostly talked about in the context of ORMs. In this kind of problem, the system needs to load N children of a one parent entity where only the parent entity was requested for.

By default, ORMs are configured with lazy-loading disabled, so one query issued for the parent entity causes N more queries, i.e. one each for N child entities.

This N+1 problem is often considered a significant performance bottleneck, and so shall be solved at the design level of the application.

2. N+1 Problem in REST APIs

Though mostly directly associated, yet the N+1 problem is not specific to ORMs only. This problem can be related to the context of web APIs as well, e.g. REST APIs.

In the case of web APIs, the N+1 problem is a situation where client applications are required to call the server N+1 times to fetch one collection resource + N child resources.

This is mostly because the collection resource did not provided enough information about the child resources to help the client application to build its user interface altogether.

For example, a REST API returning a collection of books as a resource.

<books uri="/books" size="100">
	<book uri="/books/1" id="1">
	<book uri="/books/2" id="2">
	<book uri="/books/3" id="3">

Here /books resource return list of books with information including only it’s id and isbn. This information is not enough to build a client application UI, which will want to typically show the books name in UI rather than ISBN.

In some situations, the clients may want to show other information such as the author’s name and the publication year as well.

In the above scenario, the client application MUST make N more requests for each individual book resource at /books/{id}. So in the total client will end up invoking REST APIs N+1 times.

The above scenario is only for example. The idea is that insufficient information in collection resources may lead to the N+1 problem in REST APIs.

3. How to Solve N+1 Problem

The good thing about the previously discussed problem is that we know what exactly what is the issue. And this makes the solution pretty easy.

Include enough information in single resources inside collection resources.

We may require to consult with API consumers, do the market research for similar applications and their user interfaces, or simply put ourselves in the client’s shoes.

Moreover, we may evolve our APIs over time as our understanding of client requirements improve. This is possible using API versioning.

Was this article helpful?


  1. Dunno, sounds like something that could be easily solved with an optional uri parameter or custom header e.g. “detailed”. That way you could avoid high payloads when not necessary.

  2. Great article, but you may want to include an example at the end that mimics the original example but is the solution to the problem. Explaining it is perfectly fine, but a visual example helps convey the idea better imo. In fact, maybe adding a visual to show the reduced number of requests for each example would be good too.


Leave a Comment