JavaScript Quick Tip Fetch in Parallel

One gotcha that comes up frequently and has a serious impact on application performance is the tendency to accidentally fetch data in serial that could have been fetched in parallel. Don't just drop an await in everywhere you use promises. Instead, think about the fetching dependencies. If you're fetching more than one thing, make sure you fetch in parallel whenever you can. This will make a huge difference in your application's performance.
Resources for remote software developers:
DevAnywhere - Live, remote 1:1 mentorship subscription: DevAnywhere.io
EricElliottJS.com - Learn TDD, functional programming, software design principles and JavaScript with online, interactive lessons. ericelliottjs.com
Composing Software eBook: leanpub.com/co...
Composing Software paperback: amzn.to/3biid58
---
Eric Elliott is the author of the books, “Composing Software” and “Programming JavaScript Applications”. As co-founder of EricElliottJS.com and DevAnywhere.io, he teaches developers essential software development skills. He builds and advises development teams for crypto projects, and has contributed to software experiences for Adobe Systems, Zumba Fitness, The Wall Street Journal, ESPN, BBC, and top recording artists including Usher, Frank Ocean, Metallica, and many more.
He enjoys a remote lifestyle with the most beautiful woman in the world.
#JavaScript #Code #SoftwareEngineering

[@felipezarco9502]

Good and straightforward content. Love it!

[@eyjaythejansenite3253]

I was first introduced to your work by watching your video "Classical inheritance is obsolete........". I've been learning JS, and almost every tutorial or lesson I go to always introduces classes first.
I keep going to your article and video all the time. Thank you for your work. Love these little tips.

[@franco-cespi]

Thanks for the tip. I like how you went straight to the point.

[@mihaidinul]

Thank you! Love your gpt-3 interview and hi from New Zealand!

[@rdrglpzcnt]

thank you elliot
didnt know about this

[@christazos2182]

Straight forward and really helpful. Appreciate it!

[@positivevibrations5103]

Great quick tip! Thanks!

[@hynjus001]

Damn, this is so obvious in hindsight. Feel silly for not doing this before.

[@IvoryEatsTheWorld7]

Man you´re my hero!! thanks!!

[@Anonymous-vh6kp]

Learn something new everyday! Thanks. I wonder why call in the first example don't run in parallel...

[@kostas_x]

Well, that's what the "await" keyword is all about. Each line will "await" until the async operation finishes before passing the ball to the next await operation.

[@chiragkamatkamat]

Thanks for the info 👍

[@sujitkumarsingh3200]

That's my fav. interview question but with slight twist(error cases). Which can be handled by allSettled, but I like custom implementation untill the function becomes common.

[@gabydewilde]

Of course the real answer to the riddle is that one should request everything needed in one request.

[@_ericelliott]

Not always possible, but great tip!

[@JuanPablodelaTorre]

That's the problem with async/await. It makes people think of promises as sync calls and use them in a blocking way.

[@_ericelliott]

Yep. As with all super convenient tools, there is a time and a place.

[@iamsydinh]

Thanks a lot!

[@rolfnoduk]

:-) when possible, start promises asap and await only when you *need* to use the data

[@michaelkashkov4337]

Helpful =)

[@brandyscrow]

cool