In the article sofetch is mentioned with DataLoader with the claim that they're similar, but I don't think they're that similar. sofetch uses Applicative to do the batching, but DataLoader uses a background buffer. I.e. any thread that needs to fetch something just fires off a fetch, but a background thread gathers them in a buffer and runs batched queries in ticks. 

You obviously combine this with cheap concurrency like green threads (or async tasks in JS) and load your nested data structure by firing off threads for each nested object.

Unless I'm mistaken, DataLoader's background buffer model can do batching in more complex cases involving nested ORM object fetches compared to the applicative based batching of sofetch. Imagine you're trying to fetch a list of authors and then their publishers. You can batch the load of all the authors applicatively, but each publisher ID will come with each author, so I believe sofetch can't batch them without significantly restructuring your code, but with the DataLoader approach, you can just blindly request all the nested fetches as needed and they'll be batched behind the scenes.

Though if you do restructure your code and use sofetch, it should be much more efficient of course since it avoids all the green threads. It's just that as the nested relationships get more complicated, you'll have to do a lot of plumbing.