JavaScript promises, mastering the asynchronous


Open Source Your Knowledge, Become a Contributor

Technology knowledge has to be shared and made accessible for free. Join the movement.

Create Content
Next: Why do we need asynchronous?

In JavaScript, asynchronous execution comes in multiple forms. The simplest example is shown below:

Asynchronous code using setTimeout

You can try to modify the displayed messages or the time provided to the setTimeout function. Even with a 0 millesecond delay, the asynchronous message will be displayed after the synchronous message. This is because any function given to the setTimeout function will be executed asynchronously, when the main thread is not busy anymore. You can try this code as an example:

Asynchronous code is always executed after the main thread

What can we learn from this? Simply, never trust the delay given to the setTimeout function. You can only specify a minimum delay. Even if you set a 0 delay, your code could be executed much later.

MDN documentation of setTimeout

Try this example of asynchronous code in JavaScript using setInterval:

Asynchronous code using setInterval

setInterval has the same behavior as setTimeout but the code is executed multiple times. You have to call clearInterval to kill the timer.

MDN documentation of setInterval

setTimeout and setInterval are the only native functions of the JavaScript to execute code asynchronously. However, if you are familiar with JavaScript, you have probably dealt with asynchronous execution in various forms. It can happen in multiple situations (non-exhaustive list):

  • Performing an HTTP request
  • Any I/O operation when you are in a NodeJS environment
  • Dealing with a WebSocket (client or server side)

The following code snippet is asynchronously reading a file with NodeJS:

Read a file in NodeJS
Open Source Your Knowledge: become a Contributor and help others learn. Create New Content