play.api.cache.redis.impl

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 and getOrFuture. First, both methods invoke get, then, if missed, compute orElse clause. Finally, there is the invocation of set, however, in some scenarios, there is not required to wait for the result of set operation. The value can be returned earlier. This is the difference between Eager (not waiting) and Lazy (waiting) invocation policies.

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.