Understanding Java’s Asynchronous Journey

Asynchronous programming skills are no longer “nice-to-have”; almost every programming language has it and uses it.

Languages like Go and JavaScript (in Node.js) have concurrency baked into their syntax.

Java, on the other hand, has concurrency, but it’s not quite as seamless at the syntax level when compared to something like JavaScript.

👉 If you cannot access the full article, you can read here.

For instance, take a look at how JavaScript handles asynchronous operations. It’s way more compact and arguably easier to write than Java.

function fetchData() {
  return new Promise((resolve, reject) => {
    setTimeout(() => {
      resolve('Data fetched');
    }, 10000);
  });
}

fetchData().then(data => console.log(data));
console.log('Prints first'); // prints before the resolved data

Now, this is equivalent in Java.👇

public class Example {
    public static void main(String[] args) throws ExecutionException, InterruptedException {
        CompletableFuture<String> future = CompletableFuture.supplyAsync(() -> {
            try {
                Thread.sleep(10000);
            } catch (InterruptedException e) {
                e.printStackTrace();
            }
            return "Data Fetched";
        })…