MongoDB and DataStax, In the Rearview Mirror • Hacker News Board

Re: MongoDB and DataStax, In the Rearview Mirror

#51

Post by skjhn » Wed, Jun 25, 2014, 11:01 PM UTC

trhway wrote: post #50

i don't understand - Couchbase took 1ms per operation without durability configured, ie. in memory. What took so long? Or is network roundtrip included? >However, MongoDB implements a single lock per database (link). MongoDB nodes are limited to executing a single write at a time per database. that sounds like a nightmare. Are they for real? Looking at the results - durable configs, MongoDB and DataStax, have 3ms lat…

Network roundtrip included.

Regarding MongoDB, they are. They say MongoDB 2.8 will have document level locking.

No durable configs in this benchmark though. All databases fsync'd after writes. The servers had SSDs.

Re: MongoDB and DataStax, In the Rearview Mirror

#52

Post by bkeroack » Wed, Jun 25, 2014, 11:51 PM UTC

scalesolved wrote: post #47

bkeroack wrote: post #36

Earlier quoted context omitted.

I don't have a problem with charging for support either, but Couchbase (for us) is just a memcache replacement, so that price is too high to justify. Without support the "debugging process" consists of blindly trying random things to fix the problem before giving up and moving on to something else.

The 'community' edition is free, can you run that in production? Agree on the crazy logs it generates.

We only run the community edition (everywhere). We could legally use the enterprise edition in QA, but it wouldn't make sense since production must be community.

Re: MongoDB and DataStax, In the Rearview Mirror

#53

Post by devanti » Thu, Jun 26, 2014, 4:34 AM UTC

danws6 wrote: post #23

devanti wrote: post #6

Does anyone know if Couchbase can be used as a TB sized data warehouse? Seems a bit difficult since it seems all keys must be stored in memory.

At my previous company we experimented with a 12 node cluster (128GB per node) used as a datastore. At one point we had over 1 billion keys. This was back in the 1.x version where they persisted data into sqlite files so each file would have 100+ million rows in it. Persisting data took forever. Rebalancing took forever. When it worked, it was very fast. When you lost a node, things went bad. The java client would lo…

really helpful info. thanks!

Re: MongoDB and DataStax, In the Rearview Mirror

#54

Post by devanti » Thu, Jun 26, 2014, 4:34 AM UTC

skjhn wrote: post #8

devanti wrote: post #6

Does anyone know if Couchbase can be used as a TB sized data warehouse? Seems a bit difficult since it seems all keys must be stored in memory.

It can and it is, but it might have to be scaled out. http://www.couchbase.com/liveperson http://www.couchbase.com/paypal

thanks!

Re: MongoDB and DataStax, In the Rearview Mirror

#55

Post by vosper » Thu, Jun 26, 2014, 1:53 PM UTC

shirlema wrote: post #49

vosper wrote: post #19

Earlier quoted context omitted.

Hi, thanks a lot for posting this! I have been thinking about using Couchbase Server for a mobile project because I like the mobile client component they have. I'm particularly concerned about the "opaque administration" issue - have you had to actually pay the company [1] for support because the log output is so bad, or did it just slow down your debugging process. [1] I have nothing against paying for support, but…

(grain of salt: I work in the Cassandra Community team at DataStax) If you are considering a scalable solution, you can use DataStax Enterprise for free in production if you are a startup (under $20M raised and under $2M in annual revs). Check here: http://www.datastax.com/what-we-offer/products-services/data...

Thanks for pointing this out, I'm really looking at the document store aspect of Couchbase and the automatic syncing between mobile client and server, so I don't think Cassandra would help there.