Pivotal Cloud Cache
Pivotal Cloud Cache (PCC) is a high-performance, high-availability caching layer for Pivotal Cloud Foundry (PCF). PCC offers an in-memory key-value store. It delivers low-latency responses to a large number of concurrent data access requests.
PCC provides a service broker to create in-memory data clusters on demand. These clusters are dedicated to the PCF space and tuned for specific use cases defined by your service plan. Service operators can create multiple plans to support different use cases.
PCC uses Pivotal GemFire. The Pivotal GemFire API Documentation details the API for client access to data objects within Pivotal GemFire.
This documentation performs the following functions:
- Describes the features and architecture of PCC
- Provides the PCF operator with instructions for installing, configuring, and maintaining PCC
- Provides app developers instructions for choosing a service plan, creating and deleting PCC service instances, and binding apps
The following table provides version and version-support information about PCC:
|Release date||March 8, 2018|
|Software component version||GemFire v9.3.0|
|Compatible Ops Manager version(s)||v1.10.x and v1.11.x|
|Compatible Elastic Runtime version(s)||v1.10.x and v1.11.x|
|IaaS support||AWS, Azure, GCP, OpenStack, and vSphere|
|Required BOSH stemcell version||3468.21|
|Minimum Java buildpack version required for apps||v3.13|
Some PCF services offer on-demand service plans. These plans let developers provision service instances when they want.
These contrast with the more common pre-provisioned service plans, which require operators to provision the service instances during installation and configuration through the service tile UI.
The following PCF services offer on-demand service plans:
MySQL for PCF v2.0 and later
RabbitMQ for PCF
Redis for PCF
Pivotal Cloud Cache (PCC)
These services package and deliver their on-demand service offerings differently. For example, some services, like Redis for PCF, have one tile, and you configure the tile differently depending on whether you want on-demand service plans or pre-provisioned service plans.
For other services, like PCC, you install one tile for on-demand service plans and a different tile for pre-provisioned service plans.
The following table lists and contrasts the different ways that PCF services package on-demand and pre-provisioned service offerings.
|PCF service tile||Standalone product related to the service||Versions supporting on demand||Versions supporting pre-provisioned|
|RabbitMQ for PCF||Pivotal RabbitMQ||v1.8 and later||All versions|
|Redis for PCF||Redis||v1.8 and later||All versions|
|MySQL for PCF||MySQL||v2.x
(based on Percona Server)
(based on MariaDB and Galera)
|PCC||Pivotal GemFire||All versions||NA|
|GemFire for PCF||Pivotal GemFire||NA||All versions|
PCC deploys cache clusters that use Pivotal GemFire to provide high availability, replication guarantees, and eventual consistency.
When you first spin up a cluster, you will have three locators and at least four servers.
If you scale the cluster up, you will have more servers, increasing the capacity of the cache. There always will be three locators.
When a client connects to the cluster, it first connects to a locator. The locator replies with the IP address of a server for it to talk to. The client then connects to that server.
When the client wants to read or write data, it sends a request directly to the server.
If the server doesn’t have the data locally, it fetches it from another server.
The workflow for the PCF admin setting up a PCC service plan:
- PCC can be used as a cache. It supports the look-aside cache pattern.
- PCC can be used to store objects in key/value format, where value can be any object.
- PCC works with gfsh. You can only use the gfsh version that matches this release’s version of GemFire. For the version of GemFire supported in this release, see Product Snapshot, above.
- Any gfsh command not explained in the PCC documentation is not supported.
- PCC supports basic OQL queries, with no support for joins.
- Scale down of the cluster is not supported.
- Plan migrations, for example,
-pflag with the
cf update-servicecommand, are not supported.
- WAN (Cross Data Center) replication is not supported.
- Persistent regions are not supported.
Pivotal recommends that you do the following:
- Run PCC in its own network
- Use a load balancer to block direct, outside access to the Gorouter
To allow PCC network access from apps, you must create application security groups that allow access on the following ports:
For more information, see the PCF Application Security Groups topic.
Clusters are created with two default users:
A cluster can only be accessed using one of these two users.
All client applications, gfsh, and JMX clients must authenticate as one of these users accounts to access the cluster.
Default user roles
developer have different permissions:
You can find more details about these permissions in the Pivotal GemFire Implementing Authorization topic.
Please provide any bugs, feature requests, or questions to the Pivotal Cloud Foundry Feedback list.