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.
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?
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.)
Very cool that you replied, you are one of the founders, right?
Are people directly exposing Couchbase/CouchDB at the frontend? A lot of people poo-pooed that idea (NEVER EXPOSE DB TO THE INTARWEBS!), which was the neatest idea, no matter how dangerous, when I first heard of it a few years ago. Are people doing this?
Thanks for your mobile SDKs. I wanted to learn Erlang for CouchDB, and I saw your mobile clients and thought that, and PouchDB, would make for a mean confluence of rapid desktop web and mobile app development.
It's been a long haul. In my role as an Apache volunteer I added the CouchApp capabilities into CouchDB (thanks Damien and folks for tolerating me!). After that we started a company that eventually merged with another NoSQL company to become Couchbase.
Our technology is inspired by Apache CouchDB (and in some cases compatible with it) but it is all green stack and open source.
Couchbase Server is for when you have a ton of traffic (or spiky traffic) that you can't afford to slow down. We power mission critical apps for use cases like airline booking, market making, social gaming, e-commerce, and CMS. http://www.couchbase.com/case-studies
Couchbase Mobile is a parallel effort creating peer-to-peer capable native mobile (and other edge compute) device embedded database with network aware background sync including conflict management. IBM Cloudant also uses our model and interops with our client libraries (but our Sync Gateway has an application API I think is more fun).
Thanks for the compliment! JChris started the Open Source page and I did some more clean up on it recently. I'd like to do more there soon.
By the way, on the source, it was never intended "dumping" style but just a bunch of stuff that had been slowly wired together. Yeah, we use repo and gerrit quite a bit. Check out review.couchbase.org sometime.
Maybe I am mistaken, but was Couchbase not forked by one of the original CouchDB developers, with hot paths of code rewritten in C and employing memcache to increase the speed?
EDIT: I think I confused blog posts. That is a guy involved in Couchbase, no? I forget who but one of the other CouchDB only devs who worked with him was pissed and wrote a rantish piece. Too tired to find it now.
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?