-
Notifications
You must be signed in to change notification settings - Fork 529
Architecture
brianjo edited this page Oct 14, 2014
·
22 revisions
Dynomite and the target storage engine run on the same node. Clients connect to Dynomite, and requests are proxied to either the storage engine on the same node or Dynomite processes running on other nodes.
We achieve the protocol mimicking for redis and memcache by using an open-source project from Twitter called twemproxy (AKA Nutcracker). As the request goes through a Dynomite node, the data gets replicated and eventually stored in the target storage. The data can then be read back either through Dynomite or directly from the underlying storage’s API. Twemproxy provides out of the box support for both Redis and Memcached.
- Routing
- Sharding
- Replication
- DC
- Rack
- Dynomite
- Redid/Memcache/other
- Florida (sidecard apps)