CouchDB scalability issues ? (updated)
Jonathan Ellis’ started up a storm when he posted an entry about CouchDB about 6 months ago. He questioned some of CouchDB’s claims and made an attempt to warn users who don’t understand practical issues around CoughDB very well.
After reading his post and some comments, it looked like he was specifically concerned about CouchDB’s ability to distribute/scale a growing database automatically.
Its a good read if you are curious. He has stopped accepting comments on his blog, but that shouldn’t stop you from commenting here.
As Jan pointed out in the comments Jonathan is assuming “distributed” means “auto-scaling” which is not true.
– links from the blog.. Cassandra dynomite Sawzall Pig
Related posts:
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
Hi,
to be fair, his post is about a year old and stems from misconceptions on his end IMHO. Equating “distributed” with “auto scaling” is a bit far fetched. It could be boiled down to CouchDB is not Cassandra, which is well, duh.
Cheers
Jan
–
[Translate]
It looked like a recent post when I was reading in my news reader. I’ll update the post accordingly. And I agree that he is getting confused between “distributed” and “auto scaling”. Probably a good topic to touch upon in the next few days.
[Translate]