February 1, 2012

Couchbase update

I checked in with James Phillips for a Couchbase update, and I understand better what’s going on. In particular:

If you previously heard the brand names Couchbase Single or Couchbase Mobile, pay no further attention to them. Couchbase Single was CouchDB; Couchbase Mobile is part of Couchbase’s feature set.

The current product is Couchbase 1.8, which is a whole lot like what previously was called Membase. New features in Couchbase 1.8 (versus prior versions of Membase) were concentrated in client libraries/SDK (Software Development Kit). Not coincidentally, Couchbase has hired developer evangelists who are in charge of making Couchbase play nicely with various specific languages (e.g. C/C++)

Drilling down further into the CouchDB part of the story:

There’s at least one Couchbase user with >1000 nodes (at a guess, Zynga). More typical might be 20 nodes or less. This led me to wonder how much data one puts on a Couchbase node anyway. The answer turns out to vary widely, in that you want your working set to be in RAM, and whether that’s your entire database or just a slice of it depends on the nature of the application.

James echoed a trend I’ve heard elsewhere as well, in which products one things of as being internet-specific are also sold in a few cases to conventional enterprises for — you guessed it! — their internet operations. I also asked him about competition, and he asserted:

Comments

6 Responses to “Couchbase update”

  1. Alex Popescu on February 2nd, 2012 10:47 am

    Most of the people from Couchbase (and CouchDB) have agreed that the 5 bullet points in my http://nosql.mypopescu.com/post/16348086045/couchbase-clarifying-confusions-in-5-bullet-points are cleanest way to describe the current status and the future at Couchbase.

  2. Zvi on February 2nd, 2012 8:51 pm

    No mention of Amazon DynamoDB.
    Once Redis Cluster is ready it will be a competition.

  3. Perry Krug on February 3rd, 2012 11:22 am

    Amazon DynamoDB is so new, it’s tough to make a strong comment one way or another. The difference between a service and software you manage yourself is pretty big, plus the vendor lock-in to a specific cloud. I’d look into the cost, performance and feature set of DynamoDB for comparisons…pretty sure Couchbase is still on top.

    As for Redis, even they don’t call themselves a database (they are a “data structure server”). In-memory only means you need a LOT of RAM even if all your data doesn’t need to be in RAM. Even with the Redis Cluster (which has been “coming” for a long time) we still don’t really see it as a true competitor. Certainly some use cases overlap, but we’re going for a much larger market.

    Perry

  4. Oracle preps MySQL Cluster for Web use « Download Software Service on February 15th, 2012 9:23 am

    […] “Persistent Memcached is a useful thing,” said Curt Monash of Monash Research, noting that sales of the Couchbase NoSQL database, built on Memcached, have been quite strong. […]

  5. Oracle Preps MySQL Cluster for Web Use | Got2.Me on February 15th, 2012 10:13 am

    […] “Persistent Memcached is a useful thing,” said Curt Monash of Monash Research, noting that sales of the Couchbase NoSQL database, built on Memcached, have been quite strong. […]

  6. Couchbase 2.0 | DBMS 2 : DataBase Management System Services on November 19th, 2012 9:14 pm

    […] multiple delays, Couchbase 2.0 is well into beta, with general availability being delayed by the holiday season as […]

Leave a Reply




Feed: DBMS (database management system), DW (data warehousing), BI (business intelligence), and analytics technology Subscribe to the Monash Research feed via RSS or email:

Login

Search our blogs and white papers

Monash Research blogs

User consulting

Building a short list? Refining your strategic plan? We can help.

Vendor advisory

We tell vendors what's happening -- and, more important, what they should do about it.

Monash Research highlights

Learn about white papers, webcasts, and blog highlights, by RSS or email.