[mikegioia]

It allows you to query json documents in a way similar to sql. redis is key/val and sits in ram, couch requires complicated design documents to query and is better as a key/val, but I'm unfamiliar with riak.

I think trello uses mongo primarily for production. technically it's feasible but I've found it to be more trouble than it's worth to scale -- too many machines are required per shard. I'm currently looking into rethink db as a replacement now though.

[AdrianRossouw]

I use elasticsearch to index my couch database and query it using the rest based json query language.

i find it helps being able to scale them out separately too.

http://daemon.co.za/2012/05/replacing-couchdb-views-with-ela...

[brickcap]

Hey Adrian I have got a question. Why did you chose elastic search for indexing couchdb data. Why not couchdb-lucene?

Couchdb-lucene seems more tightly integrated with couchdb to to me.

[AdrianRossouw]

I think it wasn't 'ready' at that point in time, and the json based query language was closer to what we needed.

The real problem was that the data was being imported in bulk by the user, from a many-meg-sized csv . It would grind couchdb to a halt trying to build views, so having elasticsearch be a separate process that could work through it made a lot of sense.

[brickcap]

Thanks for answering. I have used elastic search before and I was very impressed by it. Now I am trying to evaluate couchdb-lucene to see if it can prove to be a good alternative.

[h1karu]

There's no need to go through all of that trouble.. Why not just use Cloudant until the BigCouch merge hits ? :)

[AdrianRossouw]

Trouble? It's a single REST request to get a couch database continued indexed in elasticsearch in almost 'real-time'.

It just subscribes to the _changes feed and updates the index, in the same way couch replication works.

[h1karu]

I spoke too soon, seems pretty bad ass in that case. gotta love _changes

[AdrianRossouw]

yeah, it's totally overpowered. =)