7.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. The three keys are pushed to three different nodes in the cluster.

Report a bug

맨 위로 이동

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

7.2. Asynchronous API Benefits

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat 소개

Theme

Red Hat legal and privacy links

Red Hat legal and privacy links