Download Redise Pack to run it in any environment of your choice, public or private with full control over your data and configuration.
Redise Pack maintains its acclaimed seamless scaling and effortless high availability in private Platform-as-a-service environments based on CloudFoundry such as Pivotal, Bluemix and others. Redise‘s natively multi-tenant architecture is built and designed for micro-service architectures such as those used in private PaaS platforms, allowing very rapid provisioning and de-provisioning of Redis databases and requiring additional hardware only if capacity thresholds are exceeded.
Redise Tile on Pivotal Network
The Redise Tile on Pivotal Network helps Pivotal Cloud Foundry users build and deploy world-class enterprise applications with stable high performing highly available enterprise Redis from Redis Labs. Learn more.
Highlights of the integration
- Pivotal Cloud Foundry users gain access to the hassle-free, zero-downtime scaling and true high availability provided by Redise.
- Cloud Foundry administrators can provide their users with 1-click provisioning of Redise by incorporating the Redise Tile in their deployments. Redise’s efficient use of hardware means that additional hardware need not be deployed until all capacity options (using additional cores, additional memory across all servers) have been exceeded.
- Application developers and architects can incorporate the world’s most popular in-memory database platform in their applications to gain the extreme high performance and superb low latencies, both delivered with minimal operational overhead.
Learn how to install Redise on Pivotal CloudFoundry.
Redise runs in containers, and more specifically in Docker containers. Each container acts as an Redise node that can host multiple Redis shards (processes). With this, you can overcome the inherent one-to-one relationship between containers and Redis processes, and create as many Redis databases as needed, without having to add additional containers to your infrastructure.
You can also join multiple containers, each acting as an Redise node, to create an Redise cluster, for the advantages of seamless scalability and true high-availability.
In this deployment model you can achieve:
- A pure single tenant environment, by limiting the number of shards (processes) created in a single node/container
- A multi-tenant environment, by creating multiple shards (processes) in a single node/container
- A scalable and highly-available environment, by joining multiple nodes/containers into a cluster
Redise will alert you if your cluster needs more resources to scale due to shortages in processing power or memory.