lireddit VS dataloader

I just finished the React, Graphql, and typescript project by benAward. It is a 14-hour wonderful tutorial.I was thinking Are there any other videos on YT that you find very useful?Other than just a random 4-5 hour tutorial. What are some of the videos that you find very helpful?

I like this guy: https://youtu.be/I6ypD7qv3Z8

Initially I was following this Youtuber Ben's course, a full stack project which is built on Nextjs and graphql, but I know that Rest api is still the norm, and I wanna consolidate my knowledge with it, so I build these two:

I've been "learning" for awhile now so no worries. And yeah I have some old projects that broke over time because of the dependency issue too, big pain. The tech stack I've been using is based on Ben Awad's tutorial, idk if you've heard of him but you could probably pick up on how to use next.js of you go through it, pretty in depth: https://youtu.be/I6ypD7qv3Z8

Watch this and follow along https://youtu.be/I6ypD7qv3Z8

For your review, a solid day of humorous while useful info: https://youtu.be/I6ypD7qv3Z8

When I began working with GraphQL, I had concerns about the N+1 query problem. In my research, I came across the DataLoader pattern and its implementation on GitHub. While I explored various examples of its usage, I still struggled to grasp how it operates internally. Join me in delving a bit deeper into GraphQL DataLoader! :)

DataLoader: it is the standard solution to N+1 problem.

Additionally, you can use DataLoader or similar tools to optimize data fetching and avoid over-fetching or under-fetching data. Ultimately, performance and load tests ensure that your GraphQL API delivers optimal performance, meets response time expectations, and provides a smooth experience for users, even under heavy loads.

The most common practice is to turn N+1 into 1+1 using dataloaders (https://github.com/graphql/dataloader for JS, there are equivalents for most implementations). The N resolvers invoke a single batched loader which receives a list of keys and returns a list of values.

Let's take Payload, for example. Surprise, surprise. We have a relationship field, and it can store IDs to other related documents which are seamlessly merged in when you retrieve documents from the DB. We leverage the dataloader pattern to batch together all "populations" required for a given query, returning them all super fast and with as few separate queries to the DB as possible. We actually even outperform SQL-based frameworks quite a bit. In a purely relational test, we were 3x faster than Directus and 7x faster than Strapi while both were running Postgres, and we were on MongoDB.

Also, have a look at Facebook's Dataloader[0].

[0] https://github.com/graphql/dataloader

In the next article, I'm going to implement a GraphQL server with dataloader using the tools we introduced.

The one example of using Scoped dependency that comes to my mind, it's HTTP request level caching for libs like dataloader.

you would fetch these 1000 rows via dataloader that batches all requests for this relation to a single query... solving the n+1 issue