ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

CouchDB Replication Protocol and Git

Interesting parallel between CouchDB replication protocol and Git on this StackOverflow answer:

  • Like Git, records have a linked-list revision history
  • In addition to application data every record stores the evolutionary timeline of all previous revision IDs leading up to itself
  • Git isn’t really a linear list. It has forks, when one parent has multiple children. CouchDB has that too.
  • Git also has merges, when multiple children have one parent. CouchDB sort of has that too.

This is not the first time Git comes up when discussing NoSQL databases. Here’s a comparison of Git and Riak.

Original title and link: CouchDB Replication Protocol and Git (NoSQL databases © myNoSQL)