karmi | 2 years ago | on: Semantic Search with Elasticsearch, Sentence Transformers and the Quora Dataset
karmi's comments
karmi | 11 years ago | on: Elasticsearch and ruby on rails: a primer
karmi | 13 years ago | on: John Carmack on Static Code Analysis
karmi | 13 years ago | on: Create Ember.js applications with persistence in elasticsearch
karmi | 13 years ago | on: Ember.js Data Adapter for elasticsearch
But wait for an article at the http://elasticsearch.org blog with an example of a more sophisticated, Ruby-based proxy.)
karmi | 13 years ago | on: Ember.js Data Adapter for elasticsearch
karmi | 13 years ago | on: Elastic Search - Incorporated
karmi | 14 years ago | on: Flotr2 : a library for drawing HTML5 charts and graphs
karmi | 14 years ago | on: Amazon CloudSearch - Start Searching in One Hour for Less Than $100 / Month
karmi | 14 years ago | on: What happened to CouchDB's popularity?
That said, I agree with @dasil003 above that Couch played a irreplaceable role in getting people on the NoSQL track. I speak from my own experience. Compared to Mongo, Couch allowed me to wrap my head about design differences in the NoSQL world.
It's sad to see Couch fade into obscurity, but hey!, it's initial drive, it's original story (cf. the Rubyfringe video of Damien's talk), is an important part of "NoSQL archeology" for me.
karmi | 15 years ago | on: On moving from CouchDB to Riak
Note that there's a `_revs_limit` setting available: <http://wiki.apache.org/couchdb/HTTP_database_API>. It's very beneficial for a use case like yours.
(Though I've seen CouchDB performing rather poorly when taking really heavy read/write load or compacting big datasets, on occasion.)