Benchmarking Netflix Dynomite with Redis on AWS

| by Alex Giamas Follow 8 Followers on Feb 03, 2016. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

Last year, Netflix Cloud Database Engineering (CDE) team introduced Dynomite. Dynomite is a proxy layer, aiming to turn any non-distributed database into a sharded, multi-region replication aware distributed database system. Dynomite is built to provide high availability and can survive from a whole region in AWS failing through an Active-Active setup.

Netflix is already using Dynomite with Redis in their production systems. In a series of blog posts, Netflix is going through use cases and features of Dynomite. In the first one of the series, we can better understand how does Dynomite help Redis scale linearly on AWS.

Dynomite can extend the eventual consistency model to tunable consistency. The client can select consistency level of DC_ONE where reads and writes are propagated synchronously within the local Availability Zone(AZ) and asynchronously outside it. Alternatively, she can select DC_QUORUM where operations are propagated synchronously within a quorum number of nodes in the local region and asynchronously outside of it.

As shown in the tests, Dynomite can scale from 3,6,12,24 all the way through 48 nodes with linear throughput increase. This happens both in DC_ONE and in DC_QUORUM setups. Dynomite adds a minimal overhead in terms of latency, which in all tests, even with DC_QUORUM is not more than a couple of milliseconds. DC_QUORUM has higher latency and lower throughput but can provide better read and write guarantees to the client.

Finally, Dynomite also supports Redis pipelining, which can batch several requests together for a potential benefit of up to 50%. Using Dynomite, a client can improve throughput against latency, so this is something to be taken into account from the use case perspective.

The next article in the blog series, will deal with handling anti-entropy in Dynomite and how to achieve higher consistency.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you