FAQs

  • What exactly is Redise?

    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) and support for very large dataset sizes. This enhanced and exponentially more powerful database platform is called Redis enterprise, represented as Redise.

    It powers all Redis Lab’s products and services, hence they are called Redise Cloud, Redise Cloud Private, Redise Pack and Redise Pack Managed.

    We renamed our downloadable software product that was called Redis Labs Enterprise Cluster to Redise Pack, to represent the set of elements in addition to clustering and scaling that Redise adds – including a shared nothing cluster architecture, ACID compliance in distributed environments, the capability to use RAM as a Flash extender and other unique enhancements. Learn more about Redise.

  • I use open source Redis. Why should I switch to Redise Cloud?

    Redise Cloud overcomes the limitations of open source Redis. It provides scalable Redis today, even for dataset sizes beyond the size of the largest server. Moreover, it scales without the hassle of dealing with nodes and clusters, and while maintaining the same endpoints.

    Achieving true high-availability is very easy with Redise Cloud. With a click of a button, you can set up in-memory replication (in the same data center or across data centers), data persistence or remote backups.

    Redise Cloud also shields your Redis dataset from virtual environment “noisy neighbors”, resulting in stable and predictable top performance.

    And last but not least – the service is fully automated, so you do not need to worry about scaling or recovery from failures.

  • I use another commercial Redis service. Why should I switch to Redise Cloud?

    Redise Cloud is the only solution in the market offering infinite seamless scalability, true high-availability, stable top performance and zero (hassle-free) management.

    A table comparing all available commercial Redis services can be found here.

  • I am a small Redis user. Why should I switch to Redise Cloud?

    You are probably using one of those small instances to run your Redis and connect it to a small block storage volume (such as a small AWS EBS volume). You should be aware these instances and volumes were not built for the typical high-throughputs and low-latencies of Redis’ use cases. You probably also suffer occasionally from the “noisy neighbor” phenomenon, in which other cloud applications share the same physical server and storage volume with you, making your Redis performance unstable.

    Redise Cloud runs your dataset on the strongest cloud servers, so even if your dataset size is just a few megabytes, you enjoy the best performance available today. In addition, we automatically isolate “noisy neighbors,” so your Redis performance is never affected. Read here for more info.

  • Can my Redis database grow infinitely?

    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.

  • What happens when my database fills up?

    As detailed in the open source Redis FAQ, under “What happens if Redis runs out of memory?”:

    • …[you] can use the “maxmemory” option in the config file to put a limit to the memory Redis can use. If this limit is reached Redis will start to reply with an error to write commands (but will continue to accept read-only commands), or you can configure it to evict keys when the max memory limit is reached in the case you are using Redis for caching.

    Redise Cloud instances in our fixed-size plans have their maxmemory set to the plan’s size. You can easily configure an eviction policy for your instance from your account’s console and set it to any of the standard Redis behaviors without interrupting the service. Our Pay-As-You-Go plans let you set any arbitrary value for maxmemory.

  • Will my dataset/setup/endpoints be affected if I upgrade or downgrade my subscription?

    No. Any changes you make to your Redise 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.

  • Is my data safe and always available?

    Absolutely! Redise Cloud offers a comprehensive suite of high-availability provisions, including in-memory replication (within the same data center or across data centers), persistent storage and backups. Read here for more info.

  • How can I control access to my resources?

    Our premium plans feature the following access control mechanisms:

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

    We also offer custom plans with SSL authentication and encryption — contact us if you require extra security measures.

  • What’s your Service Level Agreement?

    Our SLA depends on the plan that you’re using:

    • “Cache” or “Basic” plans (no replication or data persistence) – 99.9%. In the case of node failure, there is a potential for data loss.
    • “Standard” plans (without replication, with data-persistence) – 99.9%. Data recovery time not bound by SLA.
    • “Standard” plans (with in-memory replication and data-persistence) – 99.95%
    • “Multi-AZ” plans – 99.99%
  • How many Redis databases can I create and manage?

    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. Read here for more info.

  • Why do you recommend mapping my availability zone on AWS?

    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.

  • Can I export my Redis data from Redise Cloud?

    Absolutely! There is no lock-in with Redise 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.

  • Can I run Redise Cloud on my own servers?

    Redise Cloud is a fully-managed cloud service currently offered on public clouds and PaaS only. Redise Cloud Private can be run on your own servers inside AWS VPCs. Please contact us for additional information.

  • Are you fully compatible with open source Redis?

    Yes we are. We contribute extensively to the open source Redis project and employ it in our service and, as a rule, adhere to the open source’s specifications and make every effort to update our service with its latest versions.

    That said, some of Redis’ functionality is not applicable in the context of our service – the following details these items:

    • 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 will produce an error when invoked:
    • Data persistency and backups are managed from the service’s web interface, so the following commands are blocked:
    • Since replication is managed automatically by the service and since it could present a security risk, the following commands are blocked:
    • 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 are blocked and will produce an error when invoked.
    • Commands that aren’t relevant for a hosted Redis service are blocked:

    Addtionally, 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 will result in an error:

    • 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 maximal size of key names in our service is 64KB (key values, however, can have sizes up to 512MB).

  • What are your payment schedule and terms?

    We accept all major credit cards. The first charge, when a subscription is purchased, is done immediately and is for a pro-rated amount from the day of purchase until the end of the month. Subscription renewal charges are made on the 1st of each calendar month following your subscription date. Metered usage for Pay-As-You-Go plans is charged around the 5th of each following month.

  • What exactly is Redise?

    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) and support for very large dataset sizes. This enhanced and exponentially more powerful database platform is called Redis enterprise, represented as Redise.

    It powers all Redis Lab’s products and services, hence they are called Redise Cloud, Redise Cloud Private, Redise Pack and Redise Pack Managed.

    We renamed our downloadable software product that was called Redis Labs Enterprise Cluster to Redise Pack, to represent the set of elements in addition to clustering and scaling that Redise adds – including a shared nothing cluster architecture, ACID compliance in distributed environments, the capability to use RAM as a Flash extender and other unique enhancements. Learn more about Redise.

  • I use open source Redis. Why should I switch to Redise Cloud Private?

    Self-managing a cluster of open source Redis servers can be a very demanding task, especially when your dataset is large. The ongoing operation of scaling/clustering/re-sharding/rebalancing, HA settings, recovery from failures and stabilizing performance can be quite error prone, and requires skilled personnel. Redise Cloud Private removes the heavy lifting from your DevOps/DBAs. All database operations are managed in a near fully-automated manner by our Redis experts, assuring uninterrupted database operation.

    In terms of the application, Redise Cloud Private completely hides the fact that a Redis cluster is running behind the scenes. Our production-proven zero-latency proxy resides on each node of the cluster and allows the application to access a Redis cluster as if it were accessing a single Redis instance, so there is no need to change your application code, your clients, or limit yourself to cluster-specific Redis commands.

    Redise Cloud Private also means great savings on cloud resources. You can deploy it on Flash (based on high IOPS SSD instances) and enjoy the same sub-millisecond latencies one experiences using Redis on RAM, while reducing cloud resources cost by over 70%. If your dataset is larger than 500GB, running Redis in a fully-automated manner with 24/7 expert support over RCP is lower in cost than managing your own Redis instances on the cloud.

  • I use another commercial Redis service. Why should I switch to Redise Cloud Private?

    Redise Cloud Private is the only Redis service in the market offering infinite seamless scalability (i.e. Redis cluster is supported seamlessly without the need to change your application or use a special client), true high-availability, stable top performance and zero management. Redise Cloud Private is also the only Redis service that offers Redise on Flash for substantial cloud resource cost savings.

    A table comparing all available commercial Redis services can be found here.

  • What is the difference between Redise Cloud Private and Redise Cloud?

    Redise Cloud Private(RCP) and Redise Cloud are both fully-managed Redis services operated by Redis Labs, however Redise Cloud Private runs in your own AWS Virtual Private Cloud (VPC) on dedicated and secure instances, while Redise Cloud runs on instances owned by Redis Labs’ AWS account. In addition, Redise Cloud Private offers Redison Flash, the most cost effective and high performance choice for datasets larger than 500GB. Running Redis in a fully-automated manner with 24/7 expert support over RCP is lower in cost than managing your own Redis instances on the cloud.

  • Why should I run Redise Cloud Private on Flash?

    Redis Labs’ Redise 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 Redise Cloud Private is lower in cost than managing your own Redis instances on the cloud.

  • Is my data safe and always available?

    Absolutely! Redise Cloud Private 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. Additional information can be found here.

  • How can I control access to my resources?

    Redise Cloud Private(RCP) features the following access control mechanisms:

    • Password authentication
    • Source IP/Subnet ACL
    • Security Group ACL

    When deploying RCP 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 RCP clusters. When deploying RCP on a different VPC from your application servers or under a different AWS account of yours – all the operational aspects of managing RCP are completely isolated from your application.

  • What is the Redis Labs’ Service Level Agreement?

    Our SLA (with in-memory replication and data-persistence) is 99.95% and 99.99% when deployed over multi-availability zones.

  • Can I export my Redis data from Redise Cloud Private?

    Absolutely! There is no lock-in with Redise Cloud Private. With the click of a button you can export your latest RDB backup file to AWS S3, FTP or HTTP server.

  • Are you fully compatible with open source Redis?

    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 will produce an error when invoked:
    • Data persistence and backups are managed from the service’s web interface, so the following commands are blocked:
    • Since replication is managed automatically by the service and since it could present a security risk, the following commands are blocked:
    • 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 will produce an error when invoked.
    • Commands that aren’t relevant for a hosted Redis service are blocked:
    • Additionally, only a subset of Redis’ configuration settings (via CONFIG GET/SET) is applicable to Redise Cloud. Attempts to get or set a configuration parameter that isn’t included in the following list will result in an error:
      • 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).
  • What are your payment schedule and terms?

    We charge at the beginning of each calendar month (around the 5th of the month) for the usage during the previous month. Usage is based on the size of the dataset (in GB) and its maximum throughput (in ops/sec). We accept all major credit cards.

  • What exactly is Redise?

    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) and support for very large dataset sizes. This enhanced and exponentially more powerful database platform is called Redis enterprise, represented as Redise.

    It powers all Redis Lab’s products and services, hence they are called Redise Cloud, Redise Cloud Private, Redise Pack and Redise Pack Managed.

    We renamed our downloadable software product that was called Redis Labs Enterprise Cluster to Redise Pack, to represent the set of elements in addition to clustering and scaling that Redise adds – including a shared nothing cluster architecture, ACID compliance in distributed environments, the capability to use RAM as a Flash extender and other unique enhancements. Learn more about Redise.

  • Are you fully compatible with open source Redis?

    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 will produce an error when invoked:
    • Data persistence and backups are managed from the service’s web interface, so the following commands are blocked:
    • Since replication is managed automatically by the service and since it could present a security risk, the following commands are blocked:
    • 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 will produce an error when invoked.
    • Commands that aren’t relevant for a hosted Redis service are blocked:
    • Additionally, only a subset of Redis’ configuration settings (via CONFIG GET/SET) is applicable to Redise Cloud. Attempts to get or set a configuration parameter that isn’t included in the following list will result in an error:
      • 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).
  • I use open source Redis. Why should I switch to Redise Pack?

    Redise Pack helps you overcome the limitations of open source Redis. It provides scalable Redis databases, even for datasets larger than the largest server. Moreover, it scales without the hassle of setting up or dealing with nodes and clusters, without any downtime or application changes while maintaining the same endpoints.

    Achieving true high-availability is very easy with Redise Pack. At the click of a button, you can set up in-memory replication, data persistence, and remote backups. Redise Pack protects against every type of outage with instant automatic failover and zero data loss.

    Redise Pack also shields your Redis dataset from virtual environment noises, resulting in stable and predictable top performance.

    And last but not least – it is fully automated, so there is minimal operational overhead with scaling or recovery from failures.

  • What happens when my database fills up?

    As detailed in the open source Redis FAQ, under “What happens if Redis runs out of memory?”:

    • …[you] can use the “maxmemory” option in the config file to put a limit to the memory Redis can use. If this limit is reached Redis will start to reply with an error to write commands (but will continue to accept read-only commands), or you can configure it to evict keys when the max memory limit is reached in the case you are using Redis for caching.

    You can set the maxmemory value of each Redise Pack database in the management UI using the Memory limit property, as well as configure an eviction policy by setting it to any of the standard Redis behaviors, without interrupting database operations.

  • Can I keep my data safe and always available?

    Redise Pack offers a comprehensive suite of high-availability provisions, including in-memory replication, persistent storage and backups.

  • What am I allowed to do with the free version?

    You can use the full capabilities of Redise Pack, but you cannot deploy Redise Pack to production. In addition, the free version allows a maximum of four shards. The free version does not provide the same support options as the paid version. Finally, no SLA is provided with the free version.

  • What do you mean by the term Shard?

    A shard is any type of provisioned database instance, such as a master copy, slave copy, database shard that is part of a clustered database, etc.

  • How many Redis databases can I create and manage?

    The number of databases is unlimited. The limiting factor is the available memory in the cluster, and the number of shards in the subscription. A shard is any provisioned database instance (master copy, slave copy or a database instance that is part of a clustered database).

    Note the impact of the specific database configuration on the number of shards it consumes. For example:

    • Enabling database replication, without enabling database clustering, creates two shards: a master shard and a slave shard.
    • Enabling database clustering creates as many database shards as you configure.
    • Enabling both database replication and database clustering creates double the number of database shards you configure.
  • What client can I use to connect to the databases in Redise Pack?

    Redise Pack works with all existing standard clients; it does not require you to use any special clients.

  • What are the RedisePack payment schedule and terms?

    Contact us at sales@redislabs.com to learn about Redise pricing.

  • What exactly is Redise?

    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) and support for very large dataset sizes. This enhanced and exponentially more powerful database platform is called Redis enterprise, represented as Redise.

    It powers all Redis Lab’s products and services, hence they are called Redise Cloud, Redise Cloud Private, Redise Pack and Redise Pack Managed.

    We renamed our downloadable software product that was called Redis Labs Enterprise Cluster to Redise Pack, to represent the set of elements in addition to clustering and scaling that Redise adds – including a shared nothing cluster architecture, ACID compliance in distributed environments, the capability to use RAM as a Flash extender and other unique enhancements. Learn more about Redise.

  • Are you fully compatible with open source Redis?

    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 will produce an error when invoked:
    • Data persistence and backups are managed from the service’s web interface, so the following commands are blocked:
    • Since replication is managed automatically by the service and since it could present a security risk, the following commands are blocked:
    • 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 will produce an error when invoked.
    • Commands that aren’t relevant for a hosted Redis service are blocked:
    • Additionally, only a subset of Redis’ configuration settings (via CONFIG GET/SET) is applicable to Redise Cloud. Attempts to get or set a configuration parameter that isn’t included in the following list will result in an error:
      • 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).
  • What do you mean by the term Shard?

    A shard is any type of provisioned database instance, such as a master copy, slave copy, database shard that is part of a clustered database, etc.

  • Why should I care about Memcached reliability since it is just a cache?

    Developers use Memcached because they care about their application performance. However, with unreliable Memcached, you may lose some or all of your Memcached data (part of which may have taken your app hours or days to calculate), due to: (a) a node failure; (b) a scaling event; (c) a software upgrade; or (d) a process restart.

    If memory loss occurs, your main database will be overloaded with queries, which may result in dramatic performance degradation or even a complete outage of your app.

    Furthermore, many web applications and popular platforms like Magento, Drupal and Joomla store session-cookies in Memcached without backing them up to persistent storage. Session losses due to Memcached failures could have severe implications on your business when users are forced to immediately logout and their shopping carts are flushed away (if you are running an e-commerce site).

    Memcached is not just a cache, but rather a cornerstone of your application’s performance. Its reliability should be your concern. Our Memcached Cloud’s in-memory replication capability, storage engine and instant auto-failover mechanism guarantee highly-available Memcached.

Didn't find what you were looking for? We’re Here to Help.