Skip to content

Async vs sync code

New Course Coming Soon:

Get Really Good at Git

The difference between running code synchronously or asynchronously

You might have heard that Node.js is fast because it provide asynchronous APIs for all expensive operations, like network access or filesystem.

What does having an asynchronous API mean?

If you anticipate an operation can take a lot of time, it makes sense to run it asynchronously, so other code can run in the meantime, and have a hook that’s called when that operation ends.

This is how Node.js can handle a lot more traffic than, say, PHP or Rails without using async libraries.

Most programming languages that were not traditionally async today do have 3rd party libraries that implement ways to call asynchronous code.

Otherwise what usually happens for example in PHP or Python code is that the thread blocks until the sync operation (reading from the network, writing a file..) ends.

If the code runs asynchronously, the CPU is not idle waiting for the process to complete, but it can go on with other tasks queued up until the original process is ready to move on.

Are you intimidated by Git? Can’t figure out merge vs rebase? Are you afraid of screwing up something any time you have to do something in Git? Do you rely on ChatGPT or random people’s answer on StackOverflow to fix your problems? Your coworkers are tired of explaining Git to you all the time? Git is something we all need to use, but few of us really master it. I created this course to improve your Git (and GitHub) knowledge at a radical level. A course that helps you feel less frustrated with Git. Launching Summer 2024. Join the waiting list!
→ Get my JavaScript Beginner's Handbook
→ Read my JavaScript Tutorials on The Valley of Code
→ Read my TypeScript Tutorial on The Valley of Code

Here is how can I help you: