Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

MongoDB Rules Single Node Deployments, Fails to Scale

blog.couchbase.com

Post reply on HN
Print view View original

11–20 of 31 posts

Re: MongoDB Rules Single Node Deployments, Fails to Scale

#11

Post by 616c »

I guess it is ... nice to see Couchbase again. I will not speak about them because I know little. They did open source their components, but in dumping ground style without full instrumentation, meaning they had inline instructions with a bunch of shell commands. I checked before submitting this, and it appears they have cleaned it up a lot, at least using the Android repo tool apparently. I will have to check it out.

http://www.couchbase.com/open-source

But does anyone use Apache CouchDB? I still do see it as one of the more unique NoSQL systems. I specifically loved the idea of CouchApps, and using it a neat version-controlled JS web app hosting system and document repository. I have obviously lost track over the years.

Does anyone use CouchDB seriously? Can they mention if the same raggging about giant irrecoverable disk consumption and other gripes still apply? Did anyone consider CouchDB and stick with Couchbase and can explain why?

Re: MongoDB Rules Single Node Deployments, Fails to Scale

#12

Post by T-A »

616c wrote: post #11

I guess it is ... nice to see Couchbase again. I will not speak about them because I know little. They did open source their components, but in dumping ground style without full instrumentation, meaning they had inline instructions with a bunch of shell commands. I checked before submitting this, and it appears they have cleaned it up a lot, at least using the Android repo tool apparently. I will have to check it out…

Maybe I'm misreading your question, but anyway, to prevent misunderstandings: Couchbase and CouchDB are different animals. http://www.couchbase.com/couchbase-vs-couchdb

Re: MongoDB Rules Single Node Deployments, Fails to Scale

#15

Post by towelguy »

codebeaker wrote: post #6
skjhn wrote: post #4

TLDR: MongoDB benchmarked Couchbase Server by having it perform CAS operations (read + update) while MongoDB performed basic operations (update), they used an outdated client library that is two years old, and they performed it with single node deployments.

MongoDB showing that in the years since this[1] was published that have learned nothing. Still chasing artificial benchmarks at the expensive of data safety and either personal or corporate integrity. [1]: http://pastebin.com/raw.php?i=FD3xe6Jt

Does this still applies to MongoDB 3.0? since it seems to be a rewrite with a new storage engine [1].

[1] http://www.mongodb.com/blog/post/announcing-mongodb-30

Re: MongoDB Rules Single Node Deployments, Fails to Scale

#17

Post by jchrisa »

616c wrote: post #11

I guess it is ... nice to see Couchbase again. I will not speak about them because I know little. They did open source their components, but in dumping ground style without full instrumentation, meaning they had inline instructions with a bunch of shell commands. I checked before submitting this, and it appears they have cleaned it up a lot, at least using the Android repo tool apparently. I will have to check it out…

CouchDB is growing and maturing. As far as Couchbase development goes, we use the Apache CouchDB protocol in our mobile products (and interoperate w the whole ecosystem including PouchDB.)

Our iOS Android Windows and Golang database implementations are all open source. http://developer.couchbase.com/mobile/

Re: MongoDB Rules Single Node Deployments, Fails to Scale

#18

Post by functional_test »

codebeaker wrote: post #6
skjhn wrote: post #4

TLDR: MongoDB benchmarked Couchbase Server by having it perform CAS operations (read + update) while MongoDB performed basic operations (update), they used an outdated client library that is two years old, and they performed it with single node deployments.

MongoDB showing that in the years since this[1] was published that have learned nothing. Still chasing artificial benchmarks at the expensive of data safety and either personal or corporate integrity. [1]: http://pastebin.com/raw.php?i=FD3xe6Jt

I reply to these posts on HN relatively frequently these days. These sorts of accusations about Mongo are out of hand, and not congruent with reality. I say this as someone who used MongoDB extensively.

I don't have time to address all of the problems, but let's look at #1 on his list:

1. MongoDB issues writes in unsafe ways by default in order to win benchmarks

This is objectively false. At the time, Mongo chose to turn off write confirmations by default -- this was clearly documented in many places including introductory documentation. Surely no one would have deployed a database without even a cursory skim of the docs, right? The notion that it was done to win benchmarks is baseless. Furthermore, in response to the community's reaction, the default was changed.

This is a recurring problem with the complaints about Mongo. You cannot use ad copy to evaluate a database (or any product for that matter, but definitely not something as important as your primary data store). You must read the documentation. You must do a trial run and make sure it will meet the needs of your use case.

You can't be upset about the results you didn't get from the work you didn't do.

Re: MongoDB Rules Single Node Deployments, Fails to Scale

#19

Post by wheaties »

Ok, so they used an outdated client and then used a double operation on Couchbase when comparing to MongoDB. The other part of "doesn't scale" wasn't addressed at all. I hate MongoDB with a passion (burned too many times) but even this is just FUD-like without numbers or something to back it up.

C'mon, you guys can do better than that. Just working is enough to show up Mongo. Seriously, the bar isn't that high.

Post reply on HN