The CouchDB saga continues. Klint Finley, reporting now for ServicesAngle, tells the different perspectives that Couchbase (the company resulted from the merger of Membase and CouchOne) and Cloudant (makers of scalable BigCouch based on CouchDB) have about CouchDB.

Couchbase:

“We’re not the CouchDB company, we will never be the CouchDB company,” James Phillips, senior vice president of products at Couchbase, told me in an interview. Phillips explained that Couchbase is integrating replication and mobile technology from CouchDB into Membase Server (now known as Couchbase Server) but the company has no business interest in CouchDB (though some of its employees are still committed to the project).

Cloudant:

Cloudant CEO Alan Hoffman who told me that Cloudant is still committed to the Apache CouchDB project. “If you look at the commits, I think you’ll see that our employees are doing a lot of the heavy lifting,” […] Hoffman said that he believes the project is in good shape. “The passion is through the roof. We’re firmly behind the community,” he said.

One thing I can tell from where I stand: both are wrong.

Original title and link: CouchDB Saga: Cloudant and Couchbase (NoSQL database©myNoSQL)

via: http://servicesangle.com/blog/2011/11/25/cloudant-ceo-were-still-committed-to-apache-couchdb/

Why Membase is the next step after Memcached:

Memcache is great, but once you start running low on memory (as you cache more info) lesser-used items in the cache will be destroyed to free up more space for new items. This can result in users getting logged out.  Also, if one of the servers in the pool fails or gets rebooted, all the data it was holding is lost, and then the cache must get “warmed up” again.

Membase is memcache with data persistence. The improvement of having data persistence is that if you need to bring down a server, you don’t have to worry about all that dainty, floaty data in memory that is gonna get burned. Since membase has replication built-in, you can feel free to restart a troublesome server with fear of your database getting pounded as the caches need to refill, or that a set of unlucky users will get logged out.  I’ll let you read about all the many other advantages of membase here.  It’s much more than I’ve mentioned here.

Original title and link: How to Cache PHP Sessions in Membase (NoSQL database©myNoSQL)

via: http://www.startupnextdoor.com/2011/11/how-to-cache-php-sessions-in-membase/

James Philips (Couchbase) quoted by Curt Monash:

NoSQL is simply a three-horse race between Couchbase, MongoDB, and Cassandra.

Off the top of my head I could name at least two other projects that are either having numerous deployments or are already managing huge amounts of data. And I’d bet every regular reader would figure out that I’m referring to Redis and HBase.

Original title and link: NoSQL: A Three-Horse Race (NoSQL database©myNoSQL)

via: http://www.dbms2.com/2011/10/23/nosql-notes/

1. Couchbase Single Server is the CouchDB packaging offered by Couchbase. But I think this is the first time this product came out under this name. At least the first Couchbase Server release didn’t mention it.

2. Back in December I was speculating that CouchDB could benefit of an internal cache. But the Couchbase team has found other places to improve performance:

   • IO compression for faster effective IO, reduced view generation time and reduced disk usage.
   • Asynchronous write optimizations.
   • New, higher performance and more configurable replicator

   All these improvements are explained in a separate post. Note that for measuring these improvements, the team used a derived version of the Basho’s benchmark—one of the few good NoSQL benchmarks.

3. Mathias Meyer has mentioned automatic compaction in his CouchDB post 1.0 roadmap. It is now available in the Couchbase Single Server 2.0.

4. Couchbase Single Server 2.0 adds experimental Coffeescript support.

   The addition of CoffeeScript allows you to write your view definitions, validation functions, update handles and changes filters in CoffeeScript instead of JavaScript. This allows one to develop views sans-braces and semicolons. It’s just as fast, and much easier on the eyes.

   For me CoffeeScript is just a JavaScript DSL. I’m not sure I like generic DSLs, but I’m no JavaScript expert.

5. It is great to see that Couchbase people continue to listen to the community and don’t drive their decisions by business objectives only—it might be the case that business objectives and community suggestions overlapped.

6. Last but not least, most of these changes have already been contributed back to the Apache CouchDB. This is a good sign that Couchbase team will continue to support the original CouchDB project.

Original title and link: Couchbase Single Server Important Improvements (NoSQL database©myNoSQL)

via: http://www.couchbase.org/products/couchbase-single/2-0-series

The only NoSQL name making the list is Couchbase which is still working on merging their CouchDB and Membase products.

Hadoop is included in the cloud category making me think of how valuable the SDTimes top 100 is.

Original title and link: Database & Integration: The SDTimes Top 100 for 2011 (NoSQL databases © myNoSQL)

via: http://www.sdtimes.com/content/article.aspx?ArticleID=35592&page=3