@Experimental public interface FunctionalMap<K,V> extends AutoCloseable
Lambdas passed in as parameters to functional map methods define the type of operation that is executed, but since lambdas are transparent to the internal logic, it was decided to separate the API into three types of operation: read-only, write-only, and read-write. This separation helps the user understand the group of functions and their possibilities.
This conscious decision to separate read-only, write-only and read-write interfaces helps type safety. So, if a user gets a read-only map, it can't write to it by mistake since no such APIs are exposed. The same happens with write-only maps, the user can only write and cannot make the mistake of reading from the entry view because read operations are not exposed.
Lambdas passed in to read-write and write-only operations, when
running in a cluster, must be marshallable. One option to do so is to
mark them as being
Serializable but this is expensive
in terms of payload size. Alternatively, you can provide an Infinispan
Externalizer for it which
drastically reduces the payload size. Marshallable lambdas for some of
the most popular lambda functions used by
javax.cache.Cache are available via the
MarshallableFunctions helper class.
Being an asynchronous API, all methods that return a single result,
CompletableFuture which wraps the result. To avoid
blocking, it offers the possibility to receive callbacks when the
CompletableFuture has completed, or it can be chained or composes
For those operations that return multiple results, the API returns
instances of a
Traversable interface which offers a lazy pullstyle
API for working with multiple results. Although pushstyle interfaces for
handling multiple results, such as RxJava, are fully asynchronous, they're
harder to use from a user’s perspective.
Traversable, being a lazy
pullstyle API, can still be asynchronous underneath since the user can
decide to work on the
Traversable at a later stage, and the
implementation itself can decide when to compute those results.
|Modifier and Type||Interface and Description|
Exposes read-only operations that can be executed against the functional map.
Exposes read-write operations that can be executed against the functional map.
Exposes write-only operations that can be executed against the functional map.
|Modifier and Type||Method and Description|
Functional map's name.
Functional map's status.
Tells if the underlying cache is using encoding or not
Tweak functional map executions providing
FunctionalMap<K,V> withParams(Param<?>... ps)
default boolean isEncoded()
Copyright © 2021 JBoss by Red Hat. All rights reserved.