Why I'm Walking Away From CouchDB

I just tried googling for the cached version, hoping that they were able to grab it, but interestingly they have only a screenshot of the article. It's even clear enough to read all the text, but there's no cached version. Surely the page itself would have been easier to store than an image?

Re: Why I'm Walking Away From CouchDB

#6

Post by AdrianRossouw » Fri, Jun 01, 2012, 7:26 PM UTC

I really like using ElasticSearch to index the couchdb database[1]. It allows you to scale out the data store and the search index separately, since they actually have separate concerns.

You can also do a lot of really complex queries with the elasticsearch query-dsl[2].

[1] http://daemon.co.za/2012/05/elasticsearch-5-minutes/ [2] http://www.elasticsearch.org/guide/reference/query-dsl

Re: Why I'm Walking Away From CouchDB

#7

Post by gabrtv » Fri, Jun 01, 2012, 7:26 PM UTC

While the blog is mostly down, here is a summary of the problems pointed out by the author:

1. View index updates - "Every write sets up a trap for the first reader to come along after the write"

2. Append-only database file - "Create(s) a huge operational headache", disk utilization, compaction, etc

CouchDB has always been a poor choice for write-heavy applications. Sounds to me like a case of selecting the wrong tool for the job.

Though I'm a big CouchDB fan myself, I wonder why the author didn't go with a traditional RDBMS for this application.

Re: Why I'm Walking Away From CouchDB

#8

Post by sp332 » Fri, Jun 01, 2012, 7:35 PM UTC

pwf wrote: post #5

mandreko wrote: post #3

Unfortunately it's getting hammered enough that the content is offline. Maybe that's why he's walking away from CouchDB?

I just tried googling for the cached version, hoping that they were able to grab it, but interestingly they have only a screenshot of the article. It's even clear enough to read all the text, but there's no cached version. Surely the page itself would have been easier to store than an image?

https://webcache.googleusercontent.com/search?strip=1&q=...

Re: Why I'm Walking Away From CouchDB

#9

Post by MSM » Fri, Jun 01, 2012, 8:52 PM UTC

gabrtv wrote: post #7

While the blog is mostly down, here is a summary of the problems pointed out by the author: 1. View index updates - "Every write sets up a trap for the first reader to come along after the write" 2. Append-only database file - "Create(s) a huge operational headache", disk utilization, compaction, etc CouchDB has always been a poor choice for write-heavy applications. Sounds to me like a case of selecting the wrong to…

In the next article, titled "What I look for", he mentions that he'd never use a stored proc to access data through SQL.

To me it sounds like he is almost refusing to use an RDBMS to its fullest.

Re: Why I'm Walking Away From CouchDB

#10

Post by donpdonp » Fri, Jun 01, 2012, 9:10 PM UTC

mandreko wrote: post #3

Unfortunately it's getting hammered enough that the content is offline. Maybe that's why he's walking away from CouchDB?

Sorry for the slow performance, its a very tiny fanless ITX server on a not-too-performant rails blogging app (typo). The traffic seems to have died down now.