Redis^e Pack v4.5.0 Release

We are very excited to announce the release of Redis^e Pack 4.5.0. Along with many quality improvements and overall performance enhancements, this release ushers in two major capabilities;

• Redis^e Flash (RF) version 2 is now generally available for use in production.
• Simpler IP Based Connection Management with Discovery Service using  the Redis Sentinel API.

Building Large Databases with RAM and Flash Memory in Redis^e Flash v2.0

With Redis^e Pack 4.5.0, Redis^e Flash version 2 is production ready. The new version brings performance, reliability, and stability enhancements when building large high performance databases using Flash memory.

Redis^e Flash (RF) offers users of Redis^e Pack and Redis^e Cloud Private the unique ability to operate a Redis database that spans both RAM and flash memory (SSD), but remains separate from Redis^e Pack’s persistence mechanisms. Whilst keys are always stored in RAM, RF intelligently manages the location of their values (RAM vs Flash) in the database via a LRU-based (least-recently-used) mechanism. Hot, frequently used values will be in RAM  while warm values will be ejected to flash memory. This enables you to have much larger datasets with RAM-like latency and performance, but at dramatically lower cost than an all-RAM database.

You can get an introduction to building large scale databases with Redis using Redis^e Flash in this short video or read more about building large scale databases with Redis in Redis^e Pack documentation.

New Discovery Service with Support for Redis’ Sentinel API

The Discovery Service enables simple IP based connection for Redis applications. It is compliant with the Redis Sentinel API can be queried to discover the database endpoint (IP address). When used in conjunction with Redis^e Pack’s other high availability features, the Discovery Service assists an application cope with connectivity under cluster topology changes such as node failures or shard migrations.

The Discovery Service is a distributed service with a process running on each node in the cluster and can be the authoritative source for cluster discovery. To employ it, your application utilizes a Sentinel enabled Redis client to connect to the Discovery Service and query the endpoint for the given database. The Discovery Service replies with the database’s endpoint, either internal or external, for that database. In case of a node failure, the Discovery Service is updated by the cluster manager with the new endpoint.

You can download Redis^e Pack 4.5.0 today and find more details on this release in the release notes and documentation.

• 4.5.0 Release Notes
• Redis^e Flash Documentation
• Discovery Service Documentation
• Redis^e Pack Documentation
• Discovery Service code examples