Invocation policy implements whether to wait for the operation result or not.
Aggregates all available redis APIs into a single handler.
Aggregates all available redis APIs into a single handler. This simplifies binding, construction, and accessing all APIs.
Each instance can apply its own prefix, e.g., to use multiple instances with the same redis database.
Transforms future result produced by redis implementation to the result of the desired type
Invocation policy implements whether to wait for the operation result or not. This applies only in the limited number of operations. The best examples are
getOrElse
andgetOrFuture
. First, both methods invokeget
, then, if missed, computeorElse
clause. Finally, there is the invocation ofset
, however, in some scenarios, there is not required to wait for the result ofset
operation. The value can be returned earlier. This is the difference betweenEager
(not waiting) andLazy
(waiting) invocation policies.