Create a higher-level Redis client wrapper that handles connection recovery

[felixputera]

Read me

Read this first before creating an issue:

• do not use this issue tracker to ask questions, instead use one of these channels. Questions will likely be closed without notice.
• you shall create a feature request only when it is general purpose enough.
• make sure that the feature is not already

Describe the feature

This is suggested by @pmlopes in https://groups.google.com/g/vertx/c/vZZOFtFGOlI.

To quote his suggestion:

Given that now we have a single interface for all the connection modes, single, sentinel, cluster and replication, perhaps a good contribution would be a wrapper helper that implements opinionated recovery semantics. For example, wrap the client, and register an exception handler that catches recoverable errors. In such events, queue all calls to "send" and "batch" until the underlying client is replaced with a new one.

Use cases

This will make the vertx redis client even easier to be used by end-users.

Contribution

Not decided yet.

[felixputera]

As an aside, I know that Node.js Redis clients (like https://github.com/NodeRedis/node-redis and https://github.com/luin/ioredis) have this feature implemented too.