8.2. Asynchronous API Benefits

The asynchronous API does not block, which provides multiple benefits, such as:

The guarantee of synchronous communication, with the added ability to handle failures and exceptions.
Not being required to block a thread's operations until the call completes.

These benefits allow you to better harness the parallelism in your system, for example:

Set<Future<?>> futures = new HashSet<Future<?>>();
futures.add(cache.putAsync("key1", "value1"));
futures.add(cache.putAsync("key2", "value2"));
futures.add(cache.putAsync("key3", "value3"));

Set<Future<?>> futures = new HashSet<Future<?>>();
futures.add(cache.putAsync("key1", "value1"));
futures.add(cache.putAsync("key2", "value2"));
futures.add(cache.putAsync("key3", "value3"));

Copy to Clipboard

Toggle word wrap

In the example, The following lines do not block the thread as they execute:

futures.add(cache.putAsync(key1, value1));
futures.add(cache.putAsync(key2, value2));
futures.add(cache.putAsync(key3, value3));

The remote calls from the three put operations are executed in parallel. This is particularly useful when executed in distributed mode.

Report a bug

Voltar ao topo

Este conteúdo não está disponível no idioma selecionado.

8.2. Asynchronous API Benefits

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Tornando o open source mais inclusivo

Sobre a Red Hat

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links