DataLoader - Source code walkthrough

[@JeffBarczewski]

This is fantastic Lee, I love having the background story and you provided just the right amount of detail in your walk through.

[@black_n5492]

The enthusiasm is what does it for me. You're so excited about this tool - it's contagious. Lol

[@radleyanaya9552]

Thank you for taking the time to make this! Years later and still helpful :D

[@KevinOld]

Thanks Lee for this walkthrough! Just the right amount of detail and length. Would love to see more of these!

[@vlrapatsky]

Thank you for great presentation and all explanations. It was a great idea widely adopted over time!

[@mahmoudsaada9106]

This series is so good. Please keep posting more!

[@appstratum9747]

Thanks for this, Lee. Really appreciated the code walkthrough and you rationale for the decisions you've taken.

[@AndresLobaton]

My tech lead recommend me this video, It's so good, thank you so much

[@WholeNewLevel2018]

Thanks for this awesome walkthrough

[@youcaillou]

Just watched, still valuable. Thanks!

[@jimcummins1543]

Great video Lee. Really helpful for me in understanding what exactly dataloader is doing. We've got something similar but it required us to pass a reference around and was not maintainable.

[@raselkarim2731]

Great job Lee.

[@pczern8275]

hey awesome introduction and code walkthrough through DataLoader. Appreciate it!
A lot has happened since 2016 in the GraphQL world so I just gotta ask if DataLoader is used by Facebook for the new redesign or in some other applications?

[@sanzhar.danybayev]

Wow! That's exactly what I was searching for!

[@conformist]

Very clear and concise walkthrough.
Thank you so much for making this video, please do more on some advanced topics!

[@curious-steps]

Thanks for the great explanation!

[@christopherlee4888]

Thanks for taking the time to walk through the source code!

[@minioppp]

Source code walkthrough was really helpful. I'll check out your other video, too. Thanks a lot.

[@urbancvek7120]

Amazing library and even more amazing explanation. Great job!

[@jacobmartin8665]

Thanks for the walkthrough.

[@NormanRzepka]

This was great. Thanks for taking the time to produce this video!

[@zyishai]

Incredible, thank you for the clear explanation! learned some new stuff about the micro-tasks queue ;)

[@knutkj]

At 19:38 you say that some promises have not run yet. Is that accurate to say? I thought that Promises are always hot, they run at instantiation time. If my understanding is correct, I still believe this one of the major shortcomings I see with promises over obsevables which supports a cold mode. This is also why I think the GraphQL implementation has some limitations, since it is based on the less powerful promise construct. An implementation based on observables would also have allowed support for a partially resolved graph which has advantages over the GQL subscription pattern with its async iterators.

[@jamaalwilliams8335]

Thanks Lee for this walkthrough.

[@jeremyshefer8148]

This is an amazing walk through! Thanks so much for taking the time to do this.

[@Mario.Jerkovic]

Keep up the good work. The library is really awesome.

[@ChrisWitko]

Great, waiting for more!

[@BacheneAdel]

Thanks Lee, Such an awesome Video with all the details

[@sandropucp76]

thanks, Lee. Great video

[@loganpowell]

You're a genius man.

[@jaikantchandrakumaran3423]

Thanks Lee. This was useful.

[@bernardoamorim9495]

Thanks for the great talk!

[@DecebalDobrica]

amazing work Lee, I was wondering if you would use anything like this in conjecture to a graph database,feels unnecessary maybe .

[@FatihKalifa]

Thank you so much Lee, this is really useful

[@JohnCiprian]

Thanks! This was really useful.

[@sanzhar.danybayev]

Does it mean that in the context of Node.JS, process.nextTick() will run in the end of HTTP request ? In other words once everything for this request will be done.

[@ChrisGeirman]

I've not yet checked out Relay, but this sounds similar to me. Fair to call this Relay-lite (ish)? Very much appreciate the walk through!

[@nicolasparada]

Thanks for explaining those stuff :)

[@miguelangelmayori1073]

where is the other videos about graphql

[@lgila001]

ruclips.net/video/IqtYr6RX32Q/видео.html

[@briancompton4705]

Thank you!

[@rafaelturk3779]

Brilliant!

[@OfferoC]

Neat. Thank you.

[@Filly309]

wouldn't this._queue.push({ key, resolve, reject }) just be a object literal not a tuple? I believe tuple do not use a key so it would be this._queue.push([ key, resolve, reject ]). Please correct me if I am wrong :)

[@fenghu5850]

very very very cool.....

[@RifatNabi]

Awesome 🤘👍

[@zarcosk8]

💪🏿

[@Mustafaismail22]

thank you

[@LizardanNet]

Why "var" instead of "let"

[@vasilstoyanov5465]

Because he understands function scoping ;)

[@NyttNorge]

var supports variable hoisting and is visible within the scope of the function it was defined. let is only visible in within the curly brackets it was defined and will throw an error if you try to use it if it hasn't been defined. Sometimes var is handy, especially with async functions since the var will be undefined until it has a value.

[@joan-diegorodriguez1983]

When you realise that you'll never be as smart as this kid...

[@Mike-gu8gt]

I sent you a few messages via Twitter, anything?

[@sigurgeirjonsson3315]

Great video - queuing/batching technique is very similar to what we have been using successfully with github.com/ZJONSSON/clues/blob/master/util/reptiles-client.js

[@crapthings]

neat

[@jessewright870]

This was very very helpful, thank you!