= Vert.x-redis
:toc: left

Vert.x-redis is redis client to be used with Vert.x.

This module allows data to be saved, retrieved, searched for, and deleted in a Redis. Redis is an open source, BSD
licensed, advanced key-value store. It is often referred to as a data structure server since keys can contain
strings, hashes, lists, sets and sorted sets. To use this module you must have a Redis server instance running on
your network.

Redis has a rich API and it can be organized in the following groups:

* Cluster - Commands related to cluster management, note that using most of these commands you will need a redis server with version &gt;=3.0.0
* Connection - Commands that allow you to switch DBs, connect, disconnect and authenticate to a server.
* Hashes - Commands that allow operations on hashes.
* HyperLogLog - Commands to approximating the number of distinct elements in a multiset, a HyperLogLog.
* Keys - Commands to work with Keys.
* List - Commands to work with Lists.
* Pub/Sub - Commands to create queues and pub/sub clients.
* Scripting - Commands to run Lua Scripts in redis.
* Server - Commands to manage and get server configurations.
* Sets - Commands to work with un ordered sets.
* Sorted Sets - Commands to work with sorted sets.
* Strings - Commands to work with Strings.
* Transactions - Commands to handle transaction lifecycle.

== Using Vert.x-Redis

To use the Vert.x Redis client, add the following dependency to the _dependencies_ section of your build descriptor:

* Maven (in your `pom.xml`):

[source,xml,subs="+attributes"]
----
<dependency>
<groupId>io.vertx</groupId>
<artifactId>vertx-redis-client</artifactId>
<version>${maven.version}</version>
</dependency>
----

* Gradle (in your `build.gradle` file):

[source,groovy,subs="+attributes"]
----
compile 'io.vertx:vertx-redis-client:${maven.version}'
----

== Connecting to Redis

The Redis client can operate in 3 distinct modes:

* Simple client (probably what most users need).
* Sentinel (when working with Redis in High Availability mode).
* Cluster (when working with Redis in Clustered mode).

The connection mode is selected by the factory method on the Redis interface. Regardless of the mode the client can be
configured using a `link:../dataobjects.html#RedisOptions[RedisOptions]` data object. By default some configuration values are
initialized with the following values:

* `netClientOptions`: default is `TcpKeepAlive: true`, `TcpNoDelay: true`
* `endpoint`: default is `localhost:6379`
* `masterName`: default is `mymaster`
* `role` default is `MASTER`
* `slaves` default is `NEVER`

In order to obtain a connection use the following code:

[source,scala]
----
Redis.createClient(vertx, RedisOptions()).connectFuture().onComplete{
  case Success(result) => {
    var client = result
  }
  case Failure(cause) => println("Failure")
}

----

In the configuration contains a `password` and/or a `select` database, these 2 commands will be executed automatically
once a successful connection is established to the server.

[source,scala]
----
var options = RedisOptions()
  .setPassword("abracadabra")
  .setSelect(1)


Redis.createClient(vertx, options).connectFuture().onComplete{
  case Success(result) => {
    var client = result
  }
  case Failure(cause) => println("Failure")
}

----

== Running commands

Given that the redis client is connected to the server, all commands are now possible to execute using this module.
The module offers a clean API for executing commands without the need to hand write the command itself, for example
if one wants to get a value of a key it can be done as:

[source,scala]
----
var redis = RedisAPI.api(client)

redis.getFuture("mykey").onComplete{
  case Success(result) => {
    // so something...
  }
  case Failure(cause) => println("Failure")
}

----

The response object is a generic type that allow converting from the basic redis types to your language types. For
example, if your response is of type `INTEGER` then you can get the value as any numeric primitive type `int`, `long`,
etc...

Or you can perform more complex tasks such as handling responses as iterators:

[source,scala]
----
// this is a multi redis response (think of it as an array
if (response.type() == ResponseType.MULTI) {
  response.foreach(item => {
    // do something with item...
  })

}

----

== High Availability mode

To work with high availability mode the connection creation is quite similar:

[source,scala]
----
Redis.createClient(vertx, RedisOptions()
  .setType(RedisClientType.SENTINEL)
  .setEndpoints(Set(SocketAddress.inetSocketAddress(5000, "127.0.0.1"), SocketAddress.inetSocketAddress(5001, "127.0.0.1"), SocketAddress.inetSocketAddress(5002, "127.0.0.1")))
  .setMasterName("sentinel7000")
  .setRole(RedisRole.MASTER)
).connectFuture().onComplete{
  case Success(result) => println("Success")
  case Failure(cause) => println("Failure")
}

----

What is important to notice is that in this mode, an extra connection is established to the server(s) and behind the
scenes the client will listen for events from the sentinel. When the sentinel notifies that we switched masters, then
an exception is send to the client and you can decide what to do next.

== Cluster mode

To work with cluster the connection creation is quite similar:

[source,scala]
----
var options = RedisOptions()
  .setEndpoints(Set(SocketAddress.inetSocketAddress(7000, "127.0.0.1"), SocketAddress.inetSocketAddress(7001, "127.0.0.1"), SocketAddress.inetSocketAddress(7002, "127.0.0.1"), SocketAddress.inetSocketAddress(7003, "127.0.0.1"), SocketAddress.inetSocketAddress(7004, "127.0.0.1"), SocketAddress.inetSocketAddress(7005, "127.0.0.1")))


----

In this case the configuration requires one of more members of the cluster to be known. This list will be used to ask
the cluster for the current configuration, which means if any of the listed members is not available it will be skipped.

In cluster mode a connection is established to each node and special care is needed when executing commands. It is
recommended to read redis manual in order to understand how clustering works. The client operating in this mode will do
a best effort to identify which slot is used by the executed command in order to execute it on the right node. There
could be cases where this isn't possible to identify and in that case as a best effort the command will be run on a
random node.

== Pub/Sub mode

Redis supports queues and pub/sub mode, when operated in this mode once a connection invokes a subscriber mode then
it cannot be used for running other commands than the command to leave that mode.

To start a subscriber one would do:

[source,scala]
----

Redis.createClient(vertx, RedisOptions()).connectFuture().onComplete{
  case Success(result) => {
    var client = result

    client.handler((message: io.vertx.scala.redis.client.Response) => {
      // do whatever you need to do with your message
    })
  }
  case Failure(cause) => println("Failure")
}

----

And from another place in the code publish messages to the queue:

[source,scala]
----

redis.sendFuture(Request.cmd(Command.PUBLISH).arg("channel1").arg("Hello World!")).onComplete{
  case Success(result) => {
    // published!
  }
  case Failure(cause) => println("Failure")
}

----

== Domain Sockets

Most of the examples shown connecting to a TCP sockets, however it is also possible to use Redis connecting to a UNIX
domain docket:

[source,scala]
----

Redis.createClient(vertx, SocketAddress.domainSocketAddress("/tmp/redis.sock")).connectFuture().onComplete{
  case Success(result) => {
    var client = result
  }
  case Failure(cause) => println("Failure")
}

----

Be aware that HA and cluster modes report server addresses always on TCP addresses not domain sockets. So the
combination is not possible. Not because of this client but how Redis works.

== Implementing Reconnect on Error

A typical scenario is that a user will want to reconnect to the server whenever an error occurs. The automatic reconnect
is not part of the redis client has it will force a behaviour that might not match the user expectations, for example:

1. What should happen to current in-flight requests?
2. Should the exception handler be invoked or not?
3. What if the retry will also fail?
4. Should the previous state (db, authentication, subscriptions) be restored?
5. Etc...

In order to give the user full flexibility, this decision should not be performed by the client. However a simple
reconnect with backoff timeout could be implemented as follows:

[source,scala]
----
Code not translatable
----

In this example the client object will be replaced on reconnect and the application will retry up to 16 times with a
backoff up to 1280ms. By discarding the client we ensure that all old inflight responses are lost and all new ones
will be on the new connection.