FWIW, we have been using ES as our primary datastore on two very large
commercial projects for over a year now. I started with CouchDB and
Hazelcast for a caching layer, but CouchDB (this was version 0.9 IIRC) and
didn't have a sharding story and was difficult to deploy in a cloud
environment. Plus it was sometimes inflating storage up to 10x the data we
were storing. We were also relying on Elastic Search to provide more
sophisticated query operations anyway.
So, it seemed like a bad idea to store our data in CouchDB and Elastic
Search, so we chose to drop CouchDB. When coupled with Hazelcast
(distributed cache + transaction support), the two couldn't work better
Full disclosure: until ES reaches 1.0 status, I also store all of our
persistable objects in Amazon's SimpleDB "just in case". If my S3 gateway is
trashed, I can reindex straight from SimpleDB.
tracermedia interactive http://www.tracermedia.com/
780 King Ave. #106
Columbus, OH 43212
phone: (614) 298-0774
fax: (614) 298-0776
cell: (234) 738-2492
On Tue, May 17, 2011 at 7:36 AM, Ville firstname.lastname@example.org:
I want something fast, masterless and fault-tolerant with search. I've
been considering Riak (nice but Search in beta), Cassandra (bloated?,
tedious indexing) and ES.
CouchDB could basically work for me but I've noticed that there are
people not happy with its stability, see
I'm only going to store JSON. Do you think CouchDB+ES would be better
approach instead of just ES? I don't know CouchDB that well so what
would be the advantages of using it also?
On May 17, 10:31 am, dpilato david.pil...@douane.finances.gouv.fr
I'm planning to use ES as a storage for JSON documents. The idea is to
reference each document with index/type/id and perform search queries
I was thinking about the same idea few weeks ago because ES is really
to setup and is powerful in managing automatically shards on many
Then I tried to use CouchDB as the primary document storage and activate
river to ES.
Really easy to setup. Really fast also to push documents into CouchDB.
CouchDB allows also to add attachements (such as PDF, XML, oOo, ...) to
documents. I don't know at this time how ES can handle (or not) PDF
It could be a nice design for your own needs.
So is there any reason for not using CouchDB as a storage for JSON docs ?
View this message in context:
Sent from the ElasticSearch Users mailing list archive at Nabble.com.