What happened to CouchDB's popularity? • Hacker News Board

Re: What happened to CouchDB's popularity?

#41

Post by rdtsc » Tue, Nov 01, 2011, 12:19 PM UTC

johnbender wrote: post #16

Having worked with neither of them my perception is that MongoDB has "better performance". While I would never rely on that for making decisions about which to use, I'm sure that has some real consequences, particularly where search popularity is concerned.

You just don't know about the other side of the coin -- no durability to start with. You'll be flying fast, until one day you realize your data is corrupted.

Not saying it is bad thing to optimize for speed, it is just a bit dishonest to downplay the negative effects especially after calling a product a DATA-base.

http://nosql.mypopescu.com/post/392868405/mongodb-durability...

http://blog.boxedice.com/2010/02/28/notes-from-a-production-...

Re: What happened to CouchDB's popularity?

#42

Post by mark_l_watson » Tue, Nov 01, 2011, 12:22 PM UTC

I use MongoB much more often than CouchDB, but I think that Cloudant's BigCouch open source project is great: easy to set up and a lot of scaling headroom. A nice auto sharding and replication layer on top of CouchDB.

Re: What happened to CouchDB's popularity?

#43

Post by parshap » Tue, Nov 01, 2011, 12:34 PM UTC

michaelbuckbee wrote: post #7

One of CouchDB's standout features is that it handles synchronization of data across devices (not that it doesn't potentially do other things well, but I think the conventional wisdom for a while was: "If you want to do synchronization use CouchDB.") That's nice, but I think that synchronization in general is less of a need as we've all become more and more connected and internet access has gotten more and more ubiqu…

> synch is not the killer feature it once was

I disagree. Mobile connectivity is going to continue being spotty for the foreseeable future and Couch's "store locally, sync whenever" paradigm is perfect for any application that needs to remain functional when not connected.

Re: What happened to CouchDB's popularity?

#44

Post by robterrell » Tue, Nov 01, 2011, 12:44 PM UTC

I'm using CouchDB every day and could not replace it with Mongo if I wanted to. So I guess I don't care how popular it is with others, since it solves my problems today (and it's at least popular enough to be maintained and improved).

That said, CouchBase has a huge messaging problem. It took me hours to figure out what CouchBase and all their editions were about. I'm interested in exploring their products, the write performance improvements should be huge, but their web site definitely is confusing and off-putting.

Re: What happened to CouchDB's popularity?

#45

Post by mumrah » Tue, Nov 01, 2011, 12:48 PM UTC

If we're comparing CouchDB's popularity to that of MongoDB's, it's simple - 10gen. 10gen has done a very good job generating lots of hype around their product. I believe they have people dedicated to this task (aka, evangelists). CouchBase on the other hand, has not done so well at this.

Re: What happened to CouchDB's popularity?

#46

Post by adaml_623 » Tue, Nov 01, 2011, 12:51 PM UTC

Wait what are the Y-axes on that graph!

Google Trends just looks at the term being mentioned or searched for?

So maybe half those search terms are 'How do I get MongoDB to do Foo' while perhaps the documentation for CouchDB is such that a google search is not the first thing to do.

Just my thoughts on that graph anyway.

Re: What happened to CouchDB's popularity?

#47

Post by damncabbage » Tue, Nov 01, 2011, 12:58 PM UTC

parshap wrote: post #43

michaelbuckbee wrote: post #7

One of CouchDB's standout features is that it handles synchronization of data across devices (not that it doesn't potentially do other things well, but I think the conventional wisdom for a while was: "If you want to do synchronization use CouchDB.") That's nice, but I think that synchronization in general is less of a need as we've all become more and more connected and internet access has gotten more and more ubiqu…

> synch is not the killer feature it once was I disagree. Mobile connectivity is going to continue being spotty for the foreseeable future and Couch's "store locally, sync whenever" paradigm is perfect for any application that needs to remain functional when not connected.

Agreed. I'm using CouchDB for a front-of-house ticketing system; the roving units need to sync back to main base (surviving disconnections thanks to spotty wireless). CouchDB is perfect for this.

I'm actually pretty worried about CouchDB going away. What's out there that does the equivalent (NoSQL or Relational, I don't care)?

Re: What happened to CouchDB's popularity?

#48

Post by sqrt17 » Tue, Nov 01, 2011, 1:07 PM UTC

mumrah wrote: post #45

If we're comparing CouchDB's popularity to that of MongoDB's, it's simple - 10gen. 10gen has done a very good job generating lots of hype around their product. I believe they have people dedicated to this task (aka, evangelists). CouchBase on the other hand, has not done so well at this.

It's also that CouchDB is (or at least used to be) rather slow compared to MongoDB.

10gen sure has done a lot to keep MongoDB growing despite many people having their homework (or essential customer data, or...) eaten by MongoDB; so part of it probably is attributable to better publicity.

Re: What happened to CouchDB's popularity?

#49

Post by dhimes » Tue, Nov 01, 2011, 1:16 PM UTC

epistasis wrote: post #2

About a year ago I built a prototype system on top of CouchDB, and it turned out to be very flaky when I went to install it elsewhere. The javascript engine (was it Rhino?) was super hard to install from source, and the distribution packages on Ubuntu were unreliable. I really like the concepts of CouchDB, and it's really influenced how I think about designing systems for future projects, but I was going to wait for…

I too built a prototype using couch. The thing that scares me is that the database gets really huge and has to be compacted "by hand." I'm not exactly sure when to run the compactions when lots of users are on as I understand that it can create some performance problems.

I find it's performance reliable and repeatable (with SpiderMonkey) however. I just don't fully understand its working parameters (I also wonder how much they are likely to change).

The mailing list seems excellent, FWIW.

Re: What happened to CouchDB's popularity?

#50

Post by jtmille3 » Tue, Nov 01, 2011, 1:47 PM UTC

I don't know about anyone else, but using CouchDB feels like I am writing nothing but stored procedures to return the simplest of searches in CouchDB land.

Where as MongoDB has a simple search syntax that I can create on the fly if needed in my code.