From fdcf3eb17a0b7b88d33efe79b6fc1871cb4f57fb Mon Sep 17 00:00:00 2001 From: Asutosh Padhi Date: Sun, 15 Sep 2024 18:45:03 +0530 Subject: [PATCH] Change 'CompletableFuture interface' to 'CompletableFuture class' --- README.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.adoc b/README.adoc index b11c694..52b82bc 100644 --- a/README.adoc +++ b/README.adoc @@ -21,7 +21,7 @@ asynchronous part, a feature often used when scaling services. You will build a lookup service that queries GitHub user information and retrieves data through GitHub's API. One approach to scaling services is to run expensive jobs in the background and wait for the results by using Java's -{CompletableFuture}[`CompletableFuture`] interface. Java's `CompletableFuture` is an +{CompletableFuture}[`CompletableFuture`] class. Java's `CompletableFuture` is an evolution from the regular `Future`. It makes it easy to pipeline multiple asynchronous operations and merge them into a single asynchronous computation. @@ -184,7 +184,7 @@ also tune the `Executor` to increase the `corePoolSize` attribute for instance. Essentially, the longer the task takes and the more tasks are invoked simultaneously, the more benefit you see from making things asynchronous. The trade off is handling the -`CompletableFuture` interface. It adds a layer of indirection, because you are no longer +`CompletableFuture` class. It adds a layer of indirection, because you are no longer dealing directly with the results. == Summary