Netflix/dynomite logo

Netflix/dynomite

Free

A generic dynamo implementation for different k-v storage engines

FreeFree tier
Type
Open Source
Company
Netflix

About Netflix/dynomite

Dynomite, inspired by the Dynamo whitepaper, is a thin, distributed dynamo layer that adds high availability and cross-datacenter replication to key-value storage engines. It currently supports Redis and Memcached, implementing a lightweight, efficient, and highly performant replication layer. The project aims to provide fault tolerance and multi-datacenter capabilities for engines that lack native support. Configuration is done via YAML, and it includes experimental gossip-based cluster management.

Key Features

Thin distributed layer for key-value storage engines
Supports Redis and Memcached protocols
Multi-datacenter replication for high availability
Efficient and highly performant implementation
YAML-based configuration
Experimental gossip protocol for cluster management

Pros & Cons

Pros
  • Provides high availability and replication for engines that lack native support
  • Lightweight and performant with few moving parts
  • Open source with active community from Netflix
  • Supports both Redis and Memcached out of the box
Cons
  • Gossip protocol is experimental and not recommended for production
  • Currently only supports Redis and Memcached (not other key-value stores)
  • Virtual nodes (vnodes) are not yet supported
  • Documentation and examples could be more extensive

Best For

Adding high availability to existing Redis deploymentsCross-datacenter replication for Memcached clustersBuilding a distributed, fault-tolerant caching layerEnabling disaster recovery across multiple data centers

FAQ

What storage engines does Dynomite support?
Dynomite currently supports Redis and Memcached protocols.
Does Dynomite support cross-datacenter replication?
Yes, Dynomite is designed to support multi-datacenter replication for high availability.
Is the gossip protocol production-ready?
No, gossip is experimental and disabled by default. Static tokens are recommended for production use.