3 ms·
Are you familiar with the CAP theorem? You can't have all three, but you can have 2. Most distributed datastores, pick for you which two of the three you'll ge
by roder 17y ago
Are you familiar with the CAP theorem? You can't have all three, but you can have 2. Most distributed datastores, pick for you which two of the three you'll get.
One of Riak's goals is to make the choice transparent to the user per document and let's the user select which they want. There's some more information about that on their website: http://riak.basho.com/cap.html http://riak.basho.com/cap.html
EDIT: this is good info about it too http://riak.basho.com/nyc-nosql/ http://riak.basho.com/nyc-nosql/
- mey 17y agoThe reason I asked is you brought up CouchDB isn't continuous where yours is, but you approach CAP in the same way CouchDB does. So the difference between continuous and scheduled replication is mostly syntax sugar. CouchDB can be cron scheduled to replicate across or pull from continuously in a similar fashion for similar functionality.
- roder 17y agoHmm, it's not really the difference between continuous and scheduled... Basically, Couch is a shared-nothing system, meaning, it retains all the data on one node. Then you can easily replicate (say via scheduled task w/ cron) the data from node to node. Riak is a distributed system, where each node that joins becomes part of a cluster of nodes and shares everything (data, work, etc).
- mey 17y agoOk, thanks for clarifying :)