Redis for Pivotal Platform
Page last updated:
Note: Pivotal has renamed Redis for Pivotal Cloud Foundry to Redis for Pivotal Platform.
Note: Pivotal has renamed Pivotal Cloud Foundry to Pivotal Platform.
This is documentation for Redis for Pivotal Platform. You can download the Redis for Pivotal Platform tile from Pivotal Network.
- Describes features and architecture of Redis for Pivotal Platform.
- Instructs the Pivotal Platform operator on how to install, configure, maintain, and backup Redis for Pivotal Platform.
- Instructs the app developer on how to choose a service plan, create and delete Redis service instances, and bind an app.
|Release date||August 31, 2020|
|Software component version||Redis OSS 5.0.7|
|Compatible Ops Manager version(s)||2.7, 2.8, 2.9, and 2.10|
|Compatible Pivotal Application Service version(s)||2.7, 2.8, 2.9, and 2.10|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
Redis is an easy to use, high speed key-value store that can be used as a database, cache, and message broker. It supports a range of data structures including strings, lists, hashes, sets, bitmaps, hyperloglogs, and geospatial indexes. It is easy to install and configure and is popular with engineers as a straightforward NoSQL data store. It is used for everything from a quick way to store data for development and testing through to enterprise-scale apps like Twitter.
Redis for Pivotal Platform packages Redis for easy deployment and operability.
There are two service offerings:
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.
For more information on the plans, see:
For information on recommended use cases, and the enterprise-readiness of Redis for Pivotal Platform, see Is Redis for Pivotal Platform right for your enterprise?.
For information on how to upgrade and the supported upgrade paths, see Upgrading Redis for Pivotal Platform.
The following table lists where you can find topics related to the information on this page:
|For more information about…||See…|
|Product compatibility||Upgrade Planner|
|How to upgrade Redis for Pivotal Platform||Upgrading Redis for Pivotal Platform|
|How to use Redis||Redis Documentation|
As well as Redis for Pivotal Platform, other services offer on-demand service plans. These plans let developers provision service instances when they want.
These contrast with the older pre-provisioned service plans, which require operators to provision the service instances during installation and configuration through the service tile UI.
The following table lists which service tiles offer on-demand and pre-provisioned service plans:
|Service tile||Standalone product related to the service||Supports on-demand||Supports pre-provisioned|
|RabbitMQ for Pivotal Platform||Pivotal RabbitMQ||Yes||Yes. Only recommended for test environments.|
|Redis for Pivotal Platform||Redis||Yes||Yes (shared-VM plan). Only recommended for test environments.|
|MySQL for Pivotal Platform||MySQL||Yes
|Pivotal Cloud Cache (PCC)||Pivotal GemFire||Yes||No|
For services that offer both on-demand and pre-provisioned plans, you can choose the plan you want to use when configuring the tile.
Please provide any bugs, feature requests, or questions to the Pivotal Platform Feedback list.