Many performance-related issues in Node.js applications have to do with how promises are implemented.... Tagged with node, promise, javascript, programming.

Dev.to is a community platform for developers, offering resources, discussions, and networking opportunities to empower individuals in their coding journey. Developers can learn new programming languages, frameworks, and tools, engage in discussions on best practices, and share their experiences with fellow developers to enhance their skills and grow their professional network.

Many performance-related issues in Node.js applications have to do with how promises are implemented. Async/await blocks the event loop when not correctly used. blocking it means that other parts of the application will suffer because they will not get executed on time and that affects the overall performance.

This is why your Node.js application is slow

So, what is the problem with async/await? You ask.

Does this mean related/dependent promises should block each other?

i don’t know if this article are correctly. A lot of peoples on coments discussed about point in the artcle to be or not right about try/catch,I/O blocking function, among other things. Im still confused but anyway its a good read

thanks for the reminder about looping and parallel vs sequential 👍🏻

From what I understand the article is pointing out that, when starting async operations close together in our code, we should consider if they could be started in parallel instead of sequentially. Additionally, as stated in the article comments, the event loop is not being blocked in any of its examples. This StackOverflow question offers good info on the matter: <a href="https://stackoverflow.com/questions/30823653/is-node-js-native-promise-all-processing-in-parallel-or-sequentially" target="_blank" rel="noopener nofollow">https://stackoverflow.com/questions/30823653/is-node-js-native-promise-all-processing-in-parallel-or-sequentially</a>