Develop with Redis clients

    Redis client libraries allow you to connect to Redis instances from within your application. This section provides an overview of several recommended Redis clients for popular programming and scripting languages.

    Developing applications with Active-Active databases

    Developing geo-distributed, multi-master applications can be difficult. Application developers may have to understand a large number of race conditions between updates to various sites, network, and cluster failures that could reorder the events and change the outcome of the updates performed across geo-distributed writes. Active-Active databases (formerly known as CRDB) are geo-distributed databases that span multiple Redis Enterprise Software (RS) clusters. Active-Active databases depend on multi-master replication (MMR) and Conflict-free Replicated Data Types (CRDTs) to power a simple development experience for geo-distributed applications.

    Benchmark a Redis on Flash enabled database

    Redis on Flash (RoF) on Redis Enterprise Software lets you use cost-effective Flash memory as a RAM extension for your database. But what does the performance look like as compared to a memory-only database, one stored solely in RAM? These scenarios use the memtier_benchmark utility to evaluate the performance of a Redis Enterprise Software deployment, including the trial version. The memtier_benchmark utility is located in /opt/redislabs/bin/ of Redis Enterprise Software deployments.

    CRDB-CLI Commands

    An Active-Active database (also known as CRDB or Conflict-free, Replicated DataBase) replicates your dataset across Redis Enterprise Software (RS) clusters located in geographically distributed regions. Active-Active databases allow read-write access in all locations, making them ideal for distributed applications that require the fastest response times, and also for disaster recovery. The Active-Active database on an individual cluster is called an instance. Each cluster that hosts an instance is called a participating cluster.

    Node Verification Utility (rlcheck)

    The rlcheck utility runs various health checks on an Redis Enterprise Software node and alerts on any issues found. This utility can be useful to confirm a successful installation or to verify that the node is functioning properly. You can access rlcheck from the host command-line interface (CLI). The output of rlcheck shows information specific to the host that you run it on. To open the rladmin CLI: Sign in to the Redis Enterprise Software host with an account that is a member of the redislabs operating system group.


    rladmin is a command-line utility for performing administrative tasks such as failover, migration, and endpoint binding on a Redis Enterprise Software cluster. rladmin can also edit cluster and database configurations. Some of these tasks can also be performed through the Management UI and some are unique to the rladmin CLI tool. rladmin Commands Command Description rladmin Enter the rladmin shell bind Bind an endpoint cluster Cluster management commands exit Exit rladmin shell failover Fail over a master shard to replica shard (previously slave shard) help Show available commands or specific command usage info Show current parameters for a cluster, database, node, or proxy migrate Migrate elements between nodes node Node management commands placement Configure shards placement policy recover Recover databases restart Restart database shards status Show status information suffix Suffix management tune Tune system parameters upgrade Upgrade the Redis or module version for a database verify Cluster verification reports bind rladmin bind manages the proxy policy for the cluster or a specific database.