one of couch's strong points is that it is great at giving away your data. most startup bros find that antithetical to their business model
Why the unnecessary use of "startup bros"?
What happened to CouchDB's popularity?
11–20 of 79 posts
Re: What happened to CouchDB's popularity?
#12A lot of this is the result of the confusion in the community, there is the CouchDB Apache project, then the CouchBase work and their own "Single Server" releases that don't necessarily map 1:1 to the Apache versions.
Then there is the CouchBase "Couch Server" offering which, from what little I can tell, is membase + CouchDB and their CouchDB build, according to their docs, isn't 100% 1:1 with the Apache CouchDB builds (some differences about protocol or something).
Then you have no officially maintained libraries for the different platforms which was a turn off to me the first time I cracked that egg open.
Then you have CouchBase wanting to focus Couch on the mobile-cloud story since they are the only NoSQL solution doing that , with native builds for some of the mobile platforms.
Then you have BigCouch and IrisCouch and a slew of other things I can't figure out where they fit in.
Ultimately when you enter the eco system and start digging, it is hard to figure out exactly what "CouchDB" is, where to grab binaries for your platform from and drivers for your platform.
As wavephorm pointed out, you can figure it all out with some reading and digging, but you have to persist.
It's not like Mongo, you don't just head to the official site, grab the official binary and install the official driver.
I'd also point out that CouchDB's biggest feature, the must-have feature no other NoSQL repo besides RavenDB replicates, is the master-master replication. If you don't need that, your barrier to entry with the other NoSQL solutions is much easier/straight forward.
I hope at some point the CouchDB community focuses their efforts on barriers to entries and figures out a common message for beginners they can communicate, and from there introduce the customizations for the people that need them (mobile Couch, BigCouch, etc.)
Re: What happened to CouchDB's popularity?
#13Google trends is not the sole decided of popularity.
http://www.google.com/trends?q=ruby+on+rails%2C+django&c...
Do you really think that ruby on rails has been declining in popularity since 2006?
Re: What happened to CouchDB's popularity?
#14From a rubyist's perspective, CouchDB was a major catalyst in reigniting interest in non-SQL databases—a long-standing cyclical occurrence—this time in the realm of web development.
CouchDB caused a lot of web developers to question what they really needed out of their data store, driving a lot of early popularity, but it turns out that it's not precisely what most web apps need. MongoDB seems to be designed much more to answer this question directly, rather than solving the interesting but perhaps slightly more esoteric problems that CouchDB addresses.
Re: What happened to CouchDB's popularity?
#15Google trends is not the sole decided of popularity. http://www.google.com/trends?q=ruby+on+rails%2C+django&c... Do you really think that ruby on rails has been declining in popularity since 2006?
Valid point, but the Django comparison is a red herring as most of those searches have nothing to do with the framework.
Re: What happened to CouchDB's popularity?
#16Having 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.
Re: What happened to CouchDB's popularity?
#17Google trends is not the sole decided of popularity. http://www.google.com/trends?q=ruby+on+rails%2C+django&c... Do you really think that ruby on rails has been declining in popularity since 2006?
Quite possibly. The Twitter debacle tainted RoR's reputation (fairly or not), and there is a concern that Ruby might turn out to be a flash in the pan. Django/Python is just as effective, and enterprises feel far more comfortable with Python's depth of support across the board.
Google's real fail is the event tags - a grand total of NONE relate to Django the web framework.
Re: What happened to CouchDB's popularity?
#18I think Couch simply started moving in the wrong technical direction at some point - mostly because of an unhealthy preoccupation with running on cell phones.
Re: What happened to CouchDB's popularity?
#19A lot of this is the result of the confusion in the community, there is the CouchDB Apache project, then the CouchBase work and their own "Single Server" releases that don't necessarily map 1:1 to the Apache versions. Then there is the CouchBase "Couch Server" offering which, from what little I can tell, is membase + CouchDB and their CouchDB build, according to their docs, isn't 100% 1:1 with the Apache CouchDB buil…
Couchbase offers 3 products -- Couchbase Server (which is Membase, with an instance of CouchDB for persistant storage). Couchbase Single Server (which is CouchDB plus Geocouch plus a few other addons). Couchbase Mobile (self-explanatory).
My understanding is that version 3.0 will probably merge the Membase and Couchbase products into one, so you'll have Couchbase and Couchbase mobile.
BigCouch is a separate product from the Cloudant guys, which is essentially CouchDB with an elastic sharding layer. Cloudant also sells a hosted version of BigCouch with -- I think -- a Lucene engine on top. There will likely be some overlap here between BigCouch and version 3 of Couchbase Server.
IrisCouch is a hosted version of Couchbase, with GeoCouch thrown in as well.
"Then you have no officially maintained libraries for the different platforms which was a turn off to me the first time I cracked that egg open."
I think this comes out of the initial popularity of CouchDB-- a bunch of people wrote drivers for all kinds of languages. Some of those guys work for Couchbase now. The libraries at http://www.couchbase.org/code/couchbase-single aren't comprehensive, but they do give you a good idea as to what's out there.
There was a bit of digging involved to get a lot of driver and connection information, but it seems like the Couchbase guys are doing a great job at cleaning up what was previously a scattershot list on the Apache site.
Re: What happened to CouchDB's popularity?
#20A lot of this is the result of the confusion in the community, there is the CouchDB Apache project, then the CouchBase work and their own "Single Server" releases that don't necessarily map 1:1 to the Apache versions. Then there is the CouchBase "Couch Server" offering which, from what little I can tell, is membase + CouchDB and their CouchDB build, according to their docs, isn't 100% 1:1 with the Apache CouchDB buil…
Couchbase offers 3 products -- Couchbase Server (which is Membase, with an instance of CouchDB for persistant storage). Couchbase Single Server (which is CouchDB plus Geocouch plus a few other addons). Couchbase Mobile (self-explanatory). My understanding is that version 3.0 will probably merge the Membase and Couchbase products into one, so you'll have Couchbase and Couchbase mobile. BigCouch is a separate product f…
Also, CouchDB is all REST, so many people just write their own drivers.