Using Caffeine’s AsyncLoadingCache in a Vert.x application

This document will show you how to use Caffeine’s AsyncLoadingCache in a Vert.x application.

What you will build

You will build an application that rotates images in a web page.

The images will be downloaded by the server from a public API exposed at

Each image represents an HTTP status code as a 🐱.


Images created by Tomomi Imura (@girlie_mac)

What you need

  • A text editor or IDE,

  • Java 11 or higher,

  • Maven or Gradle.

Create a project

The code of this project contains Maven and Gradle build files that are functionally equivalent.

Using Maven

Here is the content of the pom.xml file you should be using:

Using Gradle

Assuming you use Gradle with the Kotlin DSL, here is what your build.gradle.kts file should look like:

Web Page Implementation

The index.html web page consists mainly of:

  1. an <img> tag in the body, and

  2. a script that, after the page is loaded, changes the src attribute of the image.

<!DOCTYPE html>
<html lang="en">
  <meta charset="UTF-8">
  <title>Rotating Cats Page</title>
  <script type="application/javascript">
    window.onload = function () { // (2)
      const codes = [ // (3)
        200, 201, 204, 206,
        301, 302, 303, 304, 307, 308,
        401, 403, 404, 406, 407, 409, 410, 412, 416, 418, 425, 451,
        500, 501, 502, 503, 504,
      setInterval(function () { // (4)
        let img = document.getElementById("cat-img"); // (5)
        img.src = "/api/cats/" + codes[Math.floor(Math.random() * codes.length)]; // (6)
      }, 250)
  <img src="/api/cats/200" id="cat-img" alt="Cat image"/> <!--(1)-->
  1. img tag in the body with id set to cat-img

  2. run the script function when the page is loaded

  3. define some HTTP status codes

  4. schedule a function to execute periodically at a fixed-delay of 250 milliseconds

  5. retrieve the img element from the DOM using its id

  6. update the src attribute using an HTTP status code chosen randomly

Server Implementation

We will need a Vert.x Web Client instance to fetch images:

Web Client setup
    request = WebClient.create(vertx)
      .request(GET, new RequestOptions().setHost("").setPort(443).setSsl(true))

We will also need a cache because we do not want to overload the backend API:

Caffeine setup
    cache = Caffeine.newBuilder() // (1)
      .expireAfterWrite(Duration.ofMinutes(1)) // (2)
      .recordStats() // (3)
      .executor(cmd -> context.runOnContext(v -> // (4)
      .buildAsync((key, exec) -> CompletableFuture.supplyAsync(() -> { // (5)
        Future<Buffer> future = fetchCatImage(key); // (6)
        return future.toCompletionStage(); // (7)
      }, exec).thenComposeAsync(Function.identity(), exec));

    vertx.setPeriodic(20000, l -> { // (8)
      CacheStats stats = cache.synchronous().stats();"Stats: " + stats);
  1. create a cache builder

  2. configure the cache to expire items after 1 minute

  3. enable statistics recording

  4. define an executor which invokes tasks on the verticle context

  5. create an asynchronous loader, which much return a CompletableFuture, using the cache executor

  6. fetch the cat image

  7. convert the Vert.x Future to a CompletionStage

  8. log cache statistics periodically


The executor definition and the complex loader implementation are not strictly needed here.

Indeed, we will deploy a single verticle instance, bind the cache to a field and always invoke its methods from the event-loop. If that is your use-case, you may simplify the setup to:

    cache = Caffeine.newBuilder()
      .buildAsync((key, exec) -> {
        Future<Buffer> future = fetchCatImage(key);
        return future.toCompletionStage().toCompletableFuture();

If, however, you plan to deploy several instances of the verticle and to share the cache between them, stick to the previous implementation. It guarantees that the asynchronous loader is always invoked on the right context.

Fetching the cat image consists in sending the request to the backend using the corresponding HTTP status code as URI:

Fetching the image
  private Future<Buffer> fetchCatImage(int code) {
    return request.uri("/" + code)

Using Vert.x Web, creating the HTTP server for our API and static file is pretty straightforward:

Server setup
    Router router = Router.router(vertx);

      .listen(8080);"Server started on port 8080");

Here is how we will implement image request handling:

Handling image requests
  private void handleImageRequest(RoutingContext rc) {
    Integer code = Integer.valueOf(rc.pathParam("id")); // (1)
    CompletableFuture<Buffer> completableFuture = cache.get(code); // (2)
    Future<Buffer> future = Future.fromCompletionStage(completableFuture, context); // (3)
    future.onComplete(ar -> { // (4)
      if (ar.succeeded()) {
          .putHeader("Cache-Control", "no-store") // (5)
      } else {;
  1. retrieve the specified code from the request path

  2. invoke Caffeine (the image will be loaded from the backend transparently, if needed)

  3. convert the CompletableFuture returned by Caffeine to a Vert.x Future

  4. on completion, send the image bytes (or the failure) to the client

  5. instruct the browser to disable caching of the image (otherwise, it would query our server only once for a given code!)

Running the application

The CatsVerticle needs a main method:

Main method
  public static void main(String[] args) {
    Vertx vertx = Vertx.vertx(); // (1)
    vertx.deployVerticle(new CatsVerticle()); // (2)
  1. Create a Vert.x instance

  2. Deploy CatsVerticle

You can run the application from:

  1. your IDE, by running the main method from the CatsVerticle class, or

  2. with Maven: mvn compile exec:java, or

  3. with Gradle: ./gradlew run (Linux, macOS) or gradle run (Windows).

You should see the cat images rotating in the web page:


After some time, inspect the program output. You should read something like:

Mar 22, 2022 3:45:17 PM io.vertx.howtos.caffeine.CatsVerticle lambda$start$4
INFO: Stats: CacheStats{hitCount=52, missCount=28, loadSuccessCount=28, loadFailureCount=0, totalLoadTime=2514949257, evictionCount=0, evictionWeight=0}
Mar 22, 2022 3:45:37 PM io.vertx.howtos.caffeine.CatsVerticle lambda$start$4
INFO: Stats: CacheStats{hitCount=132, missCount=28, loadSuccessCount=28, loadFailureCount=0, totalLoadTime=2514949257, evictionCount=0, evictionWeight=0}
Mar 22, 2022 3:45:57 PM io.vertx.howtos.caffeine.CatsVerticle lambda$start$4
INFO: Stats: CacheStats{hitCount=212, missCount=28, loadSuccessCount=28, loadFailureCount=0, totalLoadTime=2514949257, evictionCount=0, evictionWeight=0}
Mar 22, 2022 3:46:17 PM io.vertx.howtos.caffeine.CatsVerticle lambda$start$4
INFO: Stats: CacheStats{hitCount=267, missCount=53, loadSuccessCount=52, loadFailureCount=0, totalLoadTime=3337599348, evictionCount=28, evictionWeight=28}
Mar 22, 2022 3:46:37 PM io.vertx.howtos.caffeine.CatsVerticle lambda$start$4
INFO: Stats: CacheStats{hitCount=344, missCount=56, loadSuccessCount=56, loadFailureCount=0, totalLoadTime=3480880213, evictionCount=28, evictionWeight=28}

Notice the changes in hitCount, missCount, or evictionCount.


This document covered:

  1. the Vert.x web client for making HTTP requests,

  2. the Vert.x web server and router,

  3. the integration of Caffeine’s asynchronous loading cache in a Vert.x application,

  4. Vert.x periodic tasks.

Last published: 2022-05-22 00:32:10 +0000.