Redis for PCF Services

On-Demand Service—Provides a dedicated VM running a Redis instance.
The operator can configure up to three plans with different configurations,
memory sizes, and quotas
App developers can provision an instance for any of the On-Demand plans offered
and configure certain Redis settings.

Shared-VM Service—Provides support for a number of Redis instances running
in a single VM.
It is designed for testing and development purposes only, do not use the
Shared-VM service in production environments.
The Shared-VM instances are pre-provisioned by the operator with a fixed number
of instances and memory size.
App developers can then use one of these pre-provisioned instances.

Redis for PCF with Steeltoe

To view examples of Steeltoe apps using Redis as a cache with failover,
see the Example Steeltoe App
repository in GitHub.

Warning:
The Steeltoe connector for Redis requires Redis for PCF to support Lua scripting.
Check whether the language you are using requires Lua scripting. If it does, contact your operator.
By default, Lua scripting is disabled for Redis for PCF, but a PCF operator can
change the setting to enable it by selecting the Lua Scripting checkbox in each service plan’s On-Demand Plan configuration pane.

If you do not see the tls_port field, TLS has not been enabled on your Redis service.

Bind New Apps with TLS

Follow the steps below to securely bind new apps to a Redis instance.

For new apps, cf bind-service exposes both TLS ports and non-secure ports. Custom connectors also make both ports available. To support secure service bindings, you must specify the TLS port in your app code.

Below is an example of manually selecting the TLS port for a redis_client in Ruby: