FAQs

Redis Labs has enhanced open source Redis with a technology layer that encapsulates open source Redis, while fully supporting all its commands, data structures and modules. It adds exceptional flexibility, stable high performance and unmatched resilience, as well as multiple deployment choices (public and private clouds, on-premises, hybrid, RAM-Flash combination), topology (active-active, active-passive, active-replica) and support for very large dataset sizes. This enhanced and exponentially more powerful database platform is Redis Enterprise.

Learn more about Redis Enterprise.

Yes we are. Not only are we are the home of Redis, but most of Redis’ core engineers also work for Redis Labs! We contribute extensively to the open source Redis project. As a rule, we adhere to the open source’s specifications and make every effort to update our service with its latest versions.

That said, the following Redis features are not applicable in the context of our service:

• Shared databases aren’t supported in our service given their potential negative impact on performance. We recommend using dedicated databases instead (read this post for more information). Therefore, the following commands are blocked and show an error when used:
  • MOVE
  • SELECT
• Data persistence and backups are managed from the service’s web interface, so the following commands are blocked:
  • BGREWRITEAOF
  • BGSAVE
  • LASTSAVE
  • SAVE
• Since replication is managed automatically by the service and since it could present a security risk, the following commands are blocked:
  • MIGRATE
  • REPLCONF
  • SLAVEOF
  • SYNC/PSYNC
• Redis Labs clustering technology is different than the open source Redis Cluster and supports clustering in a seamless manner that works with all standard Redis clients. As a result, all Cluster related commands are blocked and show an error when used.
• Redis Labs clustering technology allows multiple active proxies. As a result, the CLIENT ID command cannot guarantee incremental IDs between clients who connect to different nodes under multi proxy policies.
• Commands that aren’t relevant for a hosted Redis service are blocked:
  • CONFIG RESETSTAT
  • DEBUG OBJECT/SEGFAULT
  • OBJECT
  • SHUTDOWN
  • CLIENT PAUSE
  • COMMAND INFO
  • COMMAND COUNT
  • COMMAND GETKEYS
  • LATENCY LATEST
  • LATENCY HISTORY
  • LATENCY RESET
  • LATENCY GRAPH
  • LATENCY DOCTOR
  • MEMORY STATS
  • MEMORY DOCTOR
  • MEMORY MALLOC-STATS
  • MEMORY PURGE
  • MODULE LOAD
  • MODULE UNLOAD
  • MODULE LIST
• Additionally, only a subset of Redis’ configuration settings (via CONFIG GET/SET) is applicable to Redis Cloud. Attempts to get or set a configuration parameter that isn’t included in the following list show an error when used:
  • hash-max-ziplist-entries
  • hash-max-ziplist-value
  • list-max-ziplist-entries
  • list-max-ziplist-value
  • notify-keyspace-events
  • set-max-intset-entries
  • slowlog-log-slower-than (value must be larger than 1000)
  • slowlog-max-len (value must be between 128 and 1024)
  • zset-max-ziplist-entries
  • zset-max-ziplist-value
• Lastly, unlike Redis’ 512MB limit, the maximum size of key names in our service is 64KB (key values, however, can have sizes up to 512MB).

Each subscription plan (except for our free plans) enables multiple dedicated databases, each running in a dedicated process and in a non-blocking manner.

A 1GB plan for example, enables 16 dedicated databases.

Redis Cloud features the following access control mechanisms:

• Password authentication
• Source IP/Subnet ACL
• Security Group ACL (on AWS cloud)

If you use Redis Cloud on your own AWS infrastructure and deploy it on the same VPC as your application servers, we use a special set of AWS security permissions to limit access to only the instances required for running the Redis Cloud clusters. When deploying Redis Cloud on a different VPC from your application servers or under a different AWS account of yours, all the operational aspects of managing Redis Cloud are completely isolated from your application.

Absolutely! Redis Cloud offers a comprehensive suite of high-availability provisions, including in-memory replication (within the same data center or across data centers), persistent storage on EBS and backups to S3 or any file server.

Absolutely! There is no lock-in with Redis Cloud. With a click of button, you can export your latest RDB backup file from your cloud storage, FTP or HTTP server to any Redis server of your choice. Free plans do not include this capability.

Our proxy-based architecture and Dynamic Clustering technology were built from the ground up to provide scalable Redis, and to support its commands and data types at any dataset size. All you need to do is select a plan that fits your dataset’s size. If your dataset is expected to grow or occasionally varies in size, we recommend you select our Pay-As-You-Go plan, for which we charge according to your actual consumption of memory in GB/hr.

The same AWS availability zone name, when shown in different AWS accounts, does not always refer to the same underlying physical infrastructure. The mapping process lets us unambiguously identify your availability zone, so we can serve your Redis data from the same physical zone, minimizing inter-zone latencies.

No. Any changes you make to your Redis Cloud subscription are purely administrative and do not affect service to your application in any way. You can downgrade or upgrade your subscription at any time with no downtime or performance impact.

Redis Cloud Pro and Redis Cloud Essentials are both fully-managed Redis services operated by Redis Labs, however Redis Cloud Pro runs on a dedicated VPC and offers:

• Redis on Flash - Recommended for datasets larger than 500GB
• Active-Active and Active-Passive Geo Distribution
• Integration with modules
• Encryption of persistence data
• Cloud API

Running Redis in a fully-automated manner with 24/7 expert support over Redis Cloud is lower in cost than managing your own Redis instances on the cloud.

Redis Labs’ Redis on Flash technology enables you to run Redis on high IOPS SSD instances with high throughput and the same sub-millisecond latencies as RAM-based Redis. The economic benefit is dramatic:

• The cost of cloud instances required to support your database can be slashed by up to 70%, while maintaining the same blazing fast performance.
• As your data grows, and your processing needs increase, you can achieve cost-effective high speed operational and analytic processing with the versatility of Redis and the cost efficiency of Flash memory.
• If your dataset is larger than 500GB, running Redis in a fully-automated manner with 24/7 expert support over Redis Cloud is lower in cost than managing your own Redis instances on the cloud.