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

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

Couchbase Server: What is This First Release?

You’ve probably read everywhere about the Couchbase Server first release.

But what is this first release of Couchbase Server?

J. Chris Anderson[1] has been kind enough to answer this question:

  1. Today’s Couchbase server release is more or less just a clean build of the current Apache CouchDB including GeoCouch.

    In the future we may release code before it makes it through the full Apache release process, but before we do that we want to get our Q/A infrastructure up and running.

    The current version does not include yet any of the Membase elastic features. Nor does it support yet memcached protocol.

  2. In the near future there will be a release offering CouchDB Map Reduce views with the Membase speed and scalability, and memcached API.

    This is a huge value for existing Membase and memcached users, as now they will be able to query what they have stored, not just retrieve it by key.

  3. In the long run we will have a combined product that supports the CouchDB HTTP API as well as Membase’s memcapable API.

    Currently Membase has a strong set of clustering tools, but it is a plain key value store. By adding CouchDB query-ability to it, Membase users see value. A subset of CouchDB users will see value in our initial release (worry free scalability), but it won’t be until the integration work is done later this year that we offer elastic support to the full HTTP CouchDB API.

About Couchbase Server


  1. J.Chris Anderson: CouchDB committer, Couchone founder, Chief architect of mobile at Couchbase, @jchris  

  2. James Phillips: Co-founder and SVP Products for Couchbase  

Original title and link: Couchbase Server: What is This First Release? (NoSQL databases © myNoSQL)


Redis: Le système de cache parfait

I love how this sounds in French:

Après 3 ans d’une histoire d’amour fidèle avec Memcached; le serveur de cache notamment utilisé par Facebook, Youtube ou Twitter; je suis au bord de la rupture après avoir rencontré redis.

The author, Julien Crouzet, mentions three key features of Redis:

  • non-volatile data
  • performance
  • support for data types

On these points:

But Redis’ support for data types (lists, sets, sorted sets, and hashes) is not up for debate.

Original title and link: redis : Le système de cache parfait (NoSQL databases © myNoSQL)

via: http://blog.juliencrouzet.fr/484/redis-le-systeme-de-cache-parfait/


NHibernate Membase caching provider

I use NHibernate for some of my projects and being able to use a Membase cache provider for NHibernates second level cache would be very nice.

With help from Christian Dalager and my self, such a library is now available. Take a look here https://bitbucket.org/ovesen/membasecacheprovider

Membase is not used here as a persistent version of memcached, but as an elastic scalable solution.

Original title and link: NHibernate Membase caching provider (NoSQL databases © myNoSQL)

via: http://blog.ovesens.net/2011/02/nhibernate-membase-caching-provider/


Hadoop and Membase Case Study: AOL Advertising Architecture

Combining Hadoop and Membase to solve these challenges:

  1. How to analyze billions of user-related events, presented as a mix of structured and unstructured data, to infer demographic, psychographic and behavioral characteristics that are encapsulated into hundreds of millions of “cookie profiles”
  2. How to make hundreds of millions of cookie profiles available to their ad targeting platform with sub-millisecond, random read latency
  3. How to keep the user profiles fresh and current

AOL Advertising Hadoop Membase Case Study

In a much simplified form:

  • crunch (nb: read it as pre-process and prepare) tons of data with Hadoop
  • feed the results in a low latency, high throughput key-value store for serving them online

Original title and link: Hadoop and Membase Case Study: AOL Advertising Architecture (NoSQL databases © myNoSQL)

via: http://www.cloudera.com/blog/2011/02/an-emerging-data-management-architectural-pattern-behind-interactive-web-application/


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)


Membase: Pros and Cons

German Eichberger’s notes after a Membase talk:

Membase doesn’t have many of the fancy features other No-SQL databases offer. They don’t have a query language nor some map-reduce and even no automatic failover.

He goes on listing Membase pros and cons:

  • Pros:
    • memcached on steroids
    • fast
    • highly distributable
    • (kind of) consistent
    • easy administration and setup
    • uses the memcached protocol
    • “tap-interface” allowing 3rd party modules to look into all the data in the cluster

      nb: I think he’s referring to “Tap stream”: a publish/subscribe mechanism (supporting some level of filtering)

  • Cons:

    • a node will confirm that it has stored a value before it distributes it to other nodes and writes it to disk
    • a node failure requires an administrator to manually remove or restore the node
    • no details about the behavior in case of network splits
    • no support for multi-datacenter deployments

Comparing the points about with my short review of what is Membase, there might be some innacuracies in this list related to Membase writes and also node failure behavior. But I haven’t watched the talk, so maybe German is right.

Original title and link: Membase: Pros and Cons (NoSQL databases © myNoSQL)


Membase and Erlang with Matt Ingenthron

Matt Ingenthron[1] talking about Membase and Erlang (what worked and what didn’t) at Erlang Factory Lite LA:


Social Gaming and Virtual Goods Market Size

According to an eMarketer report the social gaming is expected to be $1bil business this year, with the virtual goods market reaching $653mil.

Can you say why am I posting this?

Hint: I know at least 1 NoSQL databases that is heavily used by one major player in these market. And probably other NoSQL databases will be used considering the massive amount of data the social gaming needs to handle.

Original title and link: Social Gaming and Virtual Goods Market Size (NoSQL databases © myNoSQL)


From No Cache to Membase: The Knot

Jason Sirota is telling the story of how The Knot (a media company) went from no cache to Membase passing through memcached and Gear6.

In talking to Membase and through our own research, we found that Membase solved all of our original problems, plus our new problems with Gear6.

  1. Membase provides a rich set of both GUI and programmatic tools to manage and monitor the cache.

  2. Membase not only runs on multiple physical nodes but balances keys across those nodes using the vBuckets

  3. Membase runs on Windows and can handle quite a bit more capacity (evidenced by Zynga) than we could possibly use.

  4. Membase uses both HA replication and distributed nodes for different solutions, in our case, it easily supports the 5 node-configuration

  5. Membase provides Buckets that can be configured by Port to allow different teams to have a set amount of space

  6. Hardware can be added both horizontally and vertically to a Membase cluster. However, one limitation is that all nodes have to run the same cache limit so you do need to think carefully about your node size

  7. No company is immune to going under but, in addition to their strong financial state, the risk for Membase is mitigated by two factors:

If you want the simplified version:

  • a typical story where to maintain the quality of the service, caching had to used
  • a typical story where with scale came also the need for better administration and monitoring tool
  • a typical story where op costs should be kept as much under control and even reduced if possible

What made Membase the winning solution for The Knot?

Some would say the feature set, which I’ll probably agree — pointing out though that such features can be found in other NoSQL databases too.

I’d say it’s Membase usage of a well-established protocol. That didn’t require The Knot to completely rewrite the whole persistence layer. Even if Membase would not have had all required features, using the memcached protocol made it the easiest solution to try out as no application changes were needed.

Original title and link: From No Cache to Membase: The Knot (NoSQL databases © myNoSQL)

via: http://jasonsirota.com/the-knot-cache-architecture-part-i-choosing-a?c=1


Membase Short Video Series

Membase has started a series of short videos on setting and getting up to speed with Membase. I think it’s a good idea, but calling the series “Membase for Dummies”, not so much!

So far, they’ve published:

Original title and link: Membase Short Video Series (NoSQL databases © myNoSQL)


Membase at FLOSS Weekly Podcast with James Phillips and Randal Schwartz

Podcast of James Phillips[1] talking Membase with FLOSS weekly host Randal Schwartz. Podcast can be downloaded from ☞ here or listened to online on ☞ castroller.com.

And here is another interview with James Phillips from Alan Shimel, NetworkWorld columnist and host of “The Open Network”:


  1. James Phillips: CEO Membase  ()

Original title and link: Membase at FLOSS Weekly Podcast with James Phillips and Randal Schwartz (NoSQL databases © myNoSQL)