ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

couchone: All content tagged as couchone in NoSQL databases and polyglot persistence

The Couchbase Genealogy

Looks like Matthew Aslett (the451group) had his own version of the Couchbase genealogy:

Couchbase genealogy

Credit Matt Aslett .

Original title and link: The Couchbase Genealogy (NoSQL database©myNoSQL)


History of Couch Projects

Just in case you thought someone made up the whole thing about the status of CouchDB being confusing:

History of Couch Projects

Found in Koji Kawamura‘s Introduction of CouchDB JP slides .

On the other hand I’m still trying to figure out if things in CouchDB land were more confusing than the various Hadoop versions out there. If you compare the two genealogy trees you’ll notice a reversed pattern.

Original title and link: History of Couch Projects (NoSQL database©myNoSQL)


Will Cloudant Become the CouchDB Go to Company?

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? (NoSQL database©myNoSQL)


NoSQL Companies Merger: Membase and CouchOne Becoming Couchbase

Late last night I’ve received an email asking if I could jump in a phone call to hear some exciting news. I had to say pass as it was extremely late, but replied back: “Is it a big client acquisition or M&A?”.

Before falling to sleep I was turning this question on all sides trying to figure out what the answer would be:

  • if a big client acquisition: what would be the name to make this a big announcement? After going through a couple of possibilities, I’ve decided that most probably that’s not it.
  • if a merger: what would be the other company? I’ve had a few in mind, so I’ve kept this in my list
  • if an acquisition: what would be the company interested in getting the scalable and persistent memcached solution? For this one the answer was quite clear.

Fast forward a couple of hours and I’m finding in my inbox the reply: Membase and CouchDB have merged giving birth to Couchbase. Wow!

While I haven’t complitely digested it, at first glance, this is merger based on market potential and not really on technology affinity:

  • Membase is the persistent/scalable memcached solution using the memcached custom protocol. CouchDB is using HTTP/HTTPS
  • Membase sweetspot is scaling, CouchDB’s disconnected applications
  • Membase is a key-value store, CouchDB is a document database
  • Membase is using a classical, master-slave like, replication model, CouchDB is using a P2P approach for replication

In a way, I have found the confirmation in Damien’s post:

What James had is the vision to see the great fit between the two companies. While independently we were both doing very well, we both have a lot of growing to do yet. And amazingly, the direction Membase needed to grow, we were already doing very well. And in the direction we needed to grow, Membase was already doing very well. Not only were the parts of the stack we were focusing on different and complementary; the way we built out our teams was different and complementary, as well. I’m not sure we could have planned it any better, and we didn’t plan it at all!

I wish I could stayed last night to go over this as I have so many questions. But I guess the questionon everyone’s tongue right now is: when will we see the first products? Because what is planned sounds really exciting:

In addition to the unrivaled performance, reliability and breadth of the Couchbase family, Couchbase will offer the most feature-rich NoSQL database available: the only document database with strict ACID transaction guarantees, multi-point triggers, user code execution across database nodes with scatter-gather support, indexing and query support, database views, real time map-reduce support, immediately consistent (CP) semantics within a datacenter or zone, and eventually consistent (AP) semantics between data centers or zones.

Couchbase products

Couchbase deployment architecture

Last, but not least: congratulations to both teams! I’m already watching the new website for the first release.

Other resources

  • James Phillips’ post: Hey, you got your chocolate in my peanut butter!

    The remarkable fit transcends technology alone. The cultural fit between teams is hand in glove. We are maniacally focused on building amazing technology and products that delight our users. We’re intensely competitive. And we value, more than anything else, the trust we’ve earned from customers who are managing their mission critical data with our systems. The last two months of joint integration planning have made it clear to me that we’ve assembled a rare and very talented group of people.

  • Damien Katz’ post: CouchOne + Membase = Couchbase

    Technologically, we’ll be joining the products together to create a high volume, low latency, elastic clustered Couchbase server system. A Couch that’s Simple, Fast, Elastic with all the reliability and power of CouchDB. We’ll also continue to support the Membase API, for both backwards compatibility and it’s performance advantages over HTTP. We will be the only solution out there that can scale to Zynga sized workloads and down phones and tablets and everything in between, supporting millions of users and keeping everything in sync.

  • Damien and James together: CouchOne + Membase: The Video

  • Introducing Couchbase!. Why this merger makes business sense:

    The combination of these technologies effectively combines the most advanced caching and clustering technology with the most reliable and full-featured document database technology in the industry.

  • We Heard You: CouchOne + Membase = Couchbase. Couchbase technology vision:

    In addition to the consistent developer API across products, the Couchbase family will feature automatic end-to-end synchronization based on Apache CouchDB’s killer replication technology – we call it CouchSync. Mobile Couchbase will offer developers of mobile applications a quick and easy solution for storing application data, with the ability to automatically synchronize that data back to a Couchbase cluster in the cloud or in your own data center.

  • Hacker News discussion

  • Curt Monash’s Membase and CouchOne merged to form Couchbase
  • PR announcement on TechCrunch, ReadWriteWeb, GigaOm

Original title and link: NoSQL Companies Merger: Membase and CouchOne Becoming Couchbase (NoSQL databases © myNoSQL)


CouchDB and the CouchOne Mobile Platform Podcast

A conversation with CouchOne’s Aaron Miller[1] and Nitin Borwankar[2] about the CouchDB application environment and CouchOne efforts to port it to Android and more generally to mobile platforms. The mp3 ☞ hosted by IBM developerWorks website can be downloaded from ☞ here (mp3).


  1. Aaron Miller: CouchOne engineer  ()
  2. Nitin Borwankar: CouchOne VP of Business Development  ()

Original title and link: CouchDB and the CouchOne Mobile Platform Podcast (NoSQL databases © myNoSQL)


CouchDB: Revisited Message and Why CouchOne?

Couchio CouchOne official post on the CouchDB confusing message/positioning:

CouchOne makes your web apps work in the cloud and on your phone, and keeps it all in sync. We provide support, toolkits and hosting services for Apache CouchDB, the leading open source document database. CouchDB is optimized for synchronizing applications running on the web, mobile devices or in the cloud.

Java’s “Write Once, Run Anywhere” proved not to work very well when considering server-hosted apps, desktop, and mobile, so I’m not really convinced about “CouchDB lets developers write apps one time, then easily run them and share data across the all kinds of mobile platforms.”. But I do think that data synchronization is a problem looking for solutions.

Original title and link: CouchDB: Revisited Message andWhy CouchOne? (NoSQL databases © myNoSQL)

via: http://www.couchone.com/page/why-couchone


NoSQL CouchDB founder turns to phone and cloud services

Gavin Clarke (The Register):

NoSQL start-up CouchIO is targeting mobile and clouds after just a year of trying to monetize the company’s CouchDB document store.

[…]

Rather than to replace SQLite, Katz believes that CouchDB has a future by being used in addition to SQLite — primarily on document-centric apps such as email, calendaring, scheduling, contacts, CRM, time sheets, and inventory. “That’s where Couch really shines,” Katz said.

Back to origins?[1]


  1. Before creating CouchDB, Damien Katz has been working on Lotus Notes.  ()

Original title and link for this post: NoSQL CouchDB founder turns to phone and cloud services (published on the NoSQL blog: myNoSQL)

via: http://www.theregister.co.uk/2010/09/08/couchone_couchdb_nosql_new_name/


Couchio or CouchOne?

There doesn’t seem to be a PR announcement (yet), but I’m hearing Couchio, the company started by CouchDB creators, is rebranding to CouchOne:

So, CouchDB, CouchApp, and CouchOne.

Original title and link for this post: Couchio or CouchOne? (published on the NoSQL blog: myNoSQL)