redislabs/redis-playground repository overview

⁠Redis Playground

A fast and easy way to interact with Redis and a number of its modules.

⁠Design

A GoLang HTTP/Websocket server acts as a bridge between users and multiple Redis servers. Containerized Redis servers are brought up and removed on demand.

The entire setup runs on a single machine, services are isolated from one another using docker containers.

Docker Images are pulled from our DockerHub account such that new versions of redis/modules can be brought in quickly.

When a user visits the site (playground.redislabs.com/redis or playground.redislabs.com/redislabs/<module_name>) a dedicated websocket connection is established between the user and our server, redis commands and responses will be transferred on this channel to and from a dedicated & isolated dockerized redis-server.

⁠Protection

Memory limit per db is set to 10MB Need to limit CPU as-well. Incase a docker container exists (due to Redis crashing) maintain a log for future investigation. Need to introduce a session time limit on which we remove client connection.

⁠Extensions

Users should be able to specify their own credentials (IP, Port, Username and Password), in which case a dedicated redis-connection is maintained on our server.

*it would be best if we could directly connect from the browser to redis (maybe using WebRTC data channel as a raw TCP connection).

Support auto completion similar to redis-cli.

⁠Usage

make docker_run

To resolve both overcommit_memory and Transparent Huge Pages warnings run the followings on your host

echo never > /sys/kernel/mm/transparent_hugepage/enabled
echo never > /sys/kernel/mm/transparent_hugepage/defrag
sysctl vm.overcommit_memory=1