Hi, I’ve recently been working on optimizing a GraphQL API and the age old n+1 problem and I came across this to see how Prisma does it. In the video, Tim uses Prisma’s Fluent API to fetch the related fields and he mentions that Prisma makes use of the dataloader pattern. But, based on previous testing of my API, in which I don’t use the Fluent API, the requests weren’t batched. I then converted my queries to use the Fluent API, and voila, the requests were now batched! However, there doesn’t seem to be a mention of this anywhere in the docs. It’s also mentioned that the main difference between the two is that Fluent API makes two separate requests, which could seem inefficient at first… i.e. until you realise that it batches requests (which is awesome!) In my opinion, a section could be added to differentiate between using the Fluent API and the general API and also give a brief intro to the dataloader pattern and explain how Fluent API batches requests. Thoughts?

Hey Shreyas 👋 thanks a lot for raising this! We are indeed currently already working on a docs page that explains Prisma's DataLoader in more detail (here's the GitHub issue you can follow to track this). However, I agree with you that this should be noted in the Fluent API section as well, so I created a GitHub issue that will be picked up by our docs team! Thanks again and let us know if you have any more questions 🙂

There’s also an issue here that was fixed in the latest version of Prisma i.e.

2.17.0

so could you try this on the latest version?

so I created a GitHub issue that will be picked up by our docs team!

Awesome!

This is great!