couchbase: All content tagged as couchbase in NoSQL databases and polyglot persistence
Hey, it looks like the NoSQL applications panel I’ve moderated at QCon SF 2011 went live minutes ago on InfoQ. Featuring Andy Gross (Basho), Frank Weigel (Couchbase), Matt Pfeil (DataStax), Michael Stack (StumbleUpon), Jared Rosoff (10gen), and yours truly.
It misses my opening jokes though ↩
Original title and link: NoSQL Applications Panel Video ( ©myNoSQL)
Matt Ingenthron in a forum thread:
There is quite a bit of work ongoing to optimize some of these paths, and there are some features coming to allow you to specify that you want to block until a change is durable at either the replication or the disk IO level. I believe use that internally to the server for prioritization as well.
Right now we write things as fast as we can and we constantly scan.
I think I’ve seen this before. And I thought Couchbase Server 2.0 will be using CouchDB durable persistence engine. Couchbase Server 2.0 is still in developer preview so there’s time for this to change. But some clarifications would be welcome.
Original title and link: Couchbase Server 2.0 Durability and Write Performance ( ©myNoSQL)
I read that:
- Cloudant might have raised $2.1 million (via Mass High Tech)
- Cloudant has a new CEO in Derek Schoettle (previously VP Sales at Vertica Systems, Inc.) (via PR announcement)
After Membase and CouchOne merger, I think it was the general expectation that the new formed Couchbase will carry on CouchOne promise of being the commercial supporters and service company for CouchDB. This made sense considering Couchbase has been offering a CouchDB product: Couchbase Single Server.
On the other hand this situation created a lot of confusion in the CouchDB world and Couchbase offering. It was only one week ago that Couchbase finally came out to clear the waters: they are not and won’t be a support company for CouchDB , nor will they continue offering a CouchDB-only product.
So there’s an unfilled spot in the NoSQL world: a go to company when CouchDB services and support are needed. Truth is I don’t have enough data to decide if there’s also a need in the market for it though.
But I’m wondering if Cloudant will pursue this positioning. At least that’s how I read Cloudant ex-CEO Alan Hoffman words. Or will the change of CEO also mark a change of direction?
Original title and link: Will Cloudant Become the CouchDB Go to Company? ( ©myNoSQL)
Justin Sheehy talking about the origins of Riak and Dave Smith about its future at Riak 1.0 party. A nice piece of the recent history.
A screencast demoing CRUD capabilities of the Couchbase 2.0 using the Ruby library.
The Couchbase Hadoop Connecter utilizes the Sqoop plug-in to stream data from the Couchbase system to Cloudera’s Distribution Including Apache Hadoop (CDH), enabling consistent application performance while also allowing for heavy duty MapReduce processing of the same dataset. In an interactive web application environment, such as an ad targeting platform, this ability ensures low latency and high throughput to make optimized decisions about real-time ad placement.
I’m wondering if this connector have already been used by the AOL Advertising Architecture, which is using Hadoop and Membase. In case it wasn’t how it would improve things?
Original title and link: Couchbase Hadoop Connector: Another Sqoop Example ( ©myNoSQL)
A 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.)
If only they would have listened to what I’ve been saying all this time.
Original title and link: What Happened to CouchDB’s Popularity? ( ©myNoSQL)
A 12 minutes screencast introducing the basics of Couchbase Mobile for Android applications: