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 Enterprise Cloud. Attempts to get or set a configuration parameter that isn’t included in the following list will result in an error:
- slowlog-log-slower-than (value must be larger than 1000)
- slowlog-max-len (value must be between 128 and 1024)
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).