Dynomite and RocksDB running on Docker

Dynomite is a kick ass cluster/proxy solution that provides high availability and strong consistent to databases. Dynomite was created and battle tested by Netflix using Memcached and Redis as primary store backend.

RocksDB it's a Facebook Embedded Key/Value store which is growing up a lot because of his incredible high performance and low latency.

For this blog post, I will show some simple project I create for the developers to get started with Dynomite and RocksDB together. This project uses docker and creates a Dynomite cluster using RocksDB as backend.

Let's get started...




Dynomite Super Powers

Dynomite is interesting for many reasons but one very simple and limited way to see Dynomite as a supercharged Redis with batteries included. Why not use ElastiCache(Amazon Redis managed service) well because first of all you should think twice before get fully coupled to Amazon or any public cloud vendor.  In the beginning, it might look like a good idea since you have all sorts of services that are integrated but there are many limitations and as you get a vendor LOCK IN you won't be able to get better and cheaper competitors offers and also it can be less available. I guess everybody remembers last S3 outage almost tear down the whole with it. If you have a portable solution you can run your solution in other cloud vendors like Google or Azure. Solutions like Spinnaker can help you a lot with that but they won't help you if your persistence system is fully coupled to one vendor.

IMHO because Dynomite is based on Amazon Dynamo paper still has superior clustering solution them original Redis cluster(Master/Replica) and elastiCacheit's pretty much the same cluster as OSS Redis Cluster but managed by AWS.

Another more comprehensive and correct way to see Dynomite is looking as a Generic Supercharger because as long as you have something that talks Redis protocol you can benefit from all Redis ecosystem and Dynomite as well.  There is a very nice project which helps on that front called ARDB.

Dynomite-Docker-RocksDB project

Basically this a very simple and tiny project. Where I have some bash scripts to create Dynomite clusters using ARDB and RocksDB as persistent backend. Let's see how to get started. First of all, you need to make sure you have Docker installed on your Linux.

How to install it?

git clone https://github.com/diegopacheco/dynomite-docker-rocksdb.git
cd dynomite-docker-rocksdb/

How bootstrap a simple cluster

cd dynomite-docker-rocksdb/
./dynomite-docker.sh run_single 0.5.8

Checking with Docker

You can run a docker ps to see thar are 3 images running.

$ docker ps
CONTAINER ID        IMAGE                                COMMAND                  CREATED             STATUS              PORTS                                 NAMES
ce924ebfa311        diegopacheco/dynomitedockerrocksdb   "/usr/local/dynomi..."   13 seconds ago      Up 12 seconds       8101-8102/tcp, 16379/tcp, 22222/tcp   dynomite3
b5ef6d44841b        diegopacheco/dynomitedockerrocksdb   "/usr/local/dynomi..."   14 seconds ago      Up 13 seconds       8101-8102/tcp, 16379/tcp, 22222/tcp   dynomite2
1822be0c7c01        diegopacheco/dynomitedockerrocksdb   "/usr/local/dynomi..."   14 seconds ago      Up 13 seconds       8101-8102/tcp, 16379/tcp, 22222/tcp   dynomite1

How test the cluster

In order to test the cluster we will run DCC: Dynomite Cluster Checker another side project I have to check dynomite deploys. DCC will setup a dyno client in java and connect on the cluster and perform a series of validations.

cd dynomite-docker-rocksdb/
./dynomite-docker.sh dcc_single

After DCC runs you shall see a report like this:

[
  {
    "server":"[172.18.0.101:8101:rack1:dc:100, 172.18.0.102:8101:rack2:dc:100, 172.18.0.103:8101:rack3:dc:100]",
    "seeds":"172.18.0.101:8101:rack1:dc:100|172.18.0.102:8101:rack2:dc:100|172.18.0.103:8101:rack3:dc:100",
    "insertTime":"0",
    "consistency":"true"
,  },
  {
    "server":"172.18.0.101",
    "seeds":"172.18.0.101:8101:rack1:dc:100",
    "getTime":"0",
    "consistency":"true"
,  },
  {
    "server":"172.18.0.102",
    "seeds":"172.18.0.102:8101:rack2:dc:100",
    "getTime":"0",
    "consistency":"true"
,  },
  {
    "server":"172.18.0.103",
    "seeds":"172.18.0.103:8101:rack3:dc:100",
    "getTime":"0",
    "consistency":"true"
,  }
]
}

--
TIME TO RUN: 3 seconds

Getting information about the cluster

cd dynomite-docker-rocksdb/
./dynomite-docker.sh info

You should see something like this:

$ ./dynomite-docker.sh info
Cluster 1 - Topology :
token: 100 dc: dc
  rack1 - 172.18.0.101
  rack2 - 172.18.0.102
  rack3 - 172.18.0.103
Seeds: 172.18.0.101:8101:rack1:dc:100|172.18.0.102:8101:rack2:dc:100|172.18.0.103:8101:rack3:dc:100

Avaliable Dynomite version: v0.5.8 and v0.5.9

Using Redis cli

You can also use redis-cli and connect to any node of the cluster: 172.18.0.101, 172.18.0.102 and 172.18.0.103. Here we are using port 8102 which is dynomite port.

$ redis-cli -p 8102 -h 172.18.0.101
172.18.0.101:8102> keys *
1) "DCC_dynomite_failoiverk"
172.18.0.101:8102>

That's it!

Now you have fun with Dynomite + RocksDB using docker. This is useful for:

  • Debugging
  • Testing
  • Testing Configs
  • Troubleshooting
  • General Development
view raw dynomite-docker-rocksdb.md hosted with ❤ by GitHub
Cheers,
Diego Pacheco


Popular posts from this blog

Having fun with Zig Language

Image
Zig is a general-purpose language created in 2016 by Andrew Kelly .  Zig aims to fix the issues C language has while being pragmatic and simple at the same time. Zig really shines as being simple by not having any hidden control flows, not having hidden memory allocations, no pre-processors, and no macros. Basically, it's one language and one language only. Since pre-processors and macros can get really complex and become their own universe. Sure it's not the Zig Philosophy.  Zig Compiler(Zig cc) also is a C compiler, and the interoperability from C to Zig is very good. Clearly, we can see influence from other languages like Go and Rust; however, Zig is pretty unique and different from Go and Rust.  Zig is fast. Zig is perfect for system programming. I bet we will see a lot of solutions being built in Zig. As a languages aficionado, I like to learn at least one language per year and sometimes more; Zig was my 2021 pick, did not regret it. Even if you dont use all language...
Keep reading

C Unit Testing with Check

Image
When I start on IT, several years ago(+15), C was the first language that I learned. But was not the first language I mastered and deployed in production which was...surprisingly Visual Basic 6.0. However, when I learned C or any language back on that old and arcane time noddy was into testing. However now is impossible to work professionally in any language without tests. C is a low-level language but still kicks ass and has several interesting libs/frameworks. People use to fear C a lot because of lack of syntactical sugar but once you get used to it is not that hard at all. Today I want to show how you can do Unit Testing with C. I will not show how to do Unit Testing with C++ but with C ANSI actually. We will be using Check a unit test lib for C ANSI.
read more »

Cool Retro Terminal

Image
I often don't blog about this kind of stuff. Yesterday I friend of mine showed me this awesome project called  cool-retro-term . When you work with Cloud Computing and DevOps Engineering you spend lots of time on the black screen testing things on the cloud.  When I saw this project I got very excited because it brings some nostalgy back to my life. To be 100% clearI'm not that old as my friend :-) However I share his joy into this retro terminals. This also reminds me some old games like Fallout 1 . I just this is pure fun so I'm sharing here with you guys some screenshots and also how to run on Gnome Ubuntu 17.04.
read more »