Membase simplifies name, goes GA
The company Northscale that makes the product Membase is now the company Membase that makes the product Membase. Good. Also, the product Membase has now gone GA.
I wrote back in August about Membase, and that covers most of what I think, with perhaps a couple of exceptions:
- One point I might put more weight on — by doing the same thing in memory (the well-known memcached caching system) and on disk, Membase may have a pretty slick high-performance memory-centric architecture.
- I’m getting more sympathetic to the idea of just banging objects to disk, whether via a key-value store in some other NoSQL kind of model. E.g., if somebody were to imitate Workday’s or salesforce.com’s technical architectures today — which while of course not identical are actually pretty similar — they might use a key-value store, rather than the actual choices of MySQL and Oracle respectively.
Generally, as per my recent NoSQL overview, I’m still negative about pure key-value stores. However, Membase:
- Has a roadmap to get beyond pure key-value.
- Is plug-compatible with the popular memcached.
- Has a high-performance memory-centric story.
So I can see some appealing Membase use cases.
And in case somebody is wondering why I don’t compare/contrast Membase with Basho’s key-value store Riak — beyond the obvious concerns raised by Basho’s VC down round — let me copy what I tweeted last night in response to a flamefest about same:
I’m not some symbolism-heavy figurehead that should be held responsible for all-inclusive nuance-balancing. I write about as much of what I think is interesting as I can get around to.
Related links
- A post I wrote about RYW consistency based in part on a great discussion with Basho’s Justin Sheehy.
- Two posts by Alex Popescu about Membase. The second has some technical details.
Comments
4 Responses to “Membase simplifies name, goes GA”
Leave a Reply
[…] a companion to my post about Membase last week, the company has graciously allowed me to post a rather detailed Membase slide deck. (It […]
[…] takes the place of something Membase planned to build called Node Code, which was going to overcome the limitations of a simple key-value interface. Node Code development didn’t ever really get started, and indeed was deferred for a couple […]
Membase is now Couchbase
Indeed, as per the comment and link above yours. 🙂