search

EndPointCorp / end-point-blog

End Point Dev blog
https://www.endpointdev.com/blog/
17 stars 65 forks source link

Comments for Riding the Elasticsearch River on a CouchDB: Part 1 #1067

Open phinjensen opened 6 years ago

phinjensen commented 6 years ago

Comments for https://www.endpointdev.com/blog/2015/01/riding-elasticsearch-river-on-bigcouch/ By Brian Gadoury

To enter a comment:

  1. Log in to GitHub
  2. Leave a comment on this issue.
phinjensen commented 6 years ago 
original author: Aaron Mildenstein
date: 2015-01-12T10:43:31-05:00

You should be using CouchDB rather than BigCouch.

See: http://jaxenter.com/cloudant-merges-distributed-bigcouch-code-with-apache-couchdb-106361.html

QUOTE: Database-as-a-service company Cloudant has pledged to breathe life into NoSQL database Apache CouchDB, by pushing the code behind its highly-tuned version, BigCouch into the larger open source project.

The code merger, which has been in the works for some months, allows CouchDB users to reap the rewards from the distributed database, such as cluster management, higher concurrency access performance and compactor technology, from the broader project.

After four years of production, Cloudant has ceased BigCouch development in order to participate fully in the CouchDB project. Development on the Amazon Dynamo-inspired framework began in 2008 and was initially conceived as an easier way of distributing petabytes, after Cloudant had been using CouchDB for CERN’s Large Hadron Collider to manage data. ENDQUOTE

phinjensen commented 6 years ago 
original author: Brian Gadoury
date: 2015-01-12T16:10:18-05:00

Thanks for the comment, Aaron. The original work that inspired this multi-part article is actually from 2013 and 2014, hence the use of BigCouch.

While I'm enjoying the image of riding down a river on a big couch, it sounds like I should s/BigCouch/CouchDB/g to make the article more relevant. Thanks again!