Right now we've got an engine capable of running get and set load, but it is doing synchrounus filesystem IO. We can't serve our client faster than we can read the item from disk, but we might serve other connections while we're reading the item off disk.
Happily, I've recently found an intersection of tasks that I can roll into a single, quick, unified project. Here's a small subset of my to-do list...
- build some automated Membase/Moxi cluster testing, with a large number of nodes
- show how folks can use TAP streams in Membase for great good
- learn more about that other new hot thing, nodejs
- blog more
Today is an exciting day for Membase. A number of us are attending Hadoop World 2010 in New York City, and if the event reception tonight is any indication of things to come tomorrow, it is going to be an event I’d have hated to miss. A very smart crowd of data scientists on the leading edge of applying Hadoop, and Membase, to solve some extremely interesting, and diverse, application and data management problems.
I am proud to say we have just released Membase Server 1.6 for general availability. We owe a huge debt of gratitude to our hundreds of beta users, who have worked with us over the past few months providing excellent feedback and helping us drive the product forward. Thank you!
Here are some of the things that stand out to me as we release the product to market:
Whenever I talk about Membase with candidates, employees, or friends, I feel more and more excited about what we are building and how it is going to impact the industry. Each discussion validates my belief that what we do *is* unique and a game changer. Just today, we had two important “wins,” one from a prospect who evaluated our technology against other NoSQL databases and chose Membase. I can’t talk much about it yet, but this is an amazing win. The second is the fact that IDC chose us as an innovative company to watch. Great day!
I am working full time on membase, which utilize the "engine interface" we're adding to Memcached. Being the one who designed the API and wrote the documentation, I can say that we do need more (and better) documentation without insulting anyone.
Winning awards is always fun. Over the years, companies I’ve been part of have won their fair share. But not all awards are created equal. Some definitely carry more weight than others, and I put the IDC Innovative Company to Watch award in this category. The fact that IDC does extensive research on the markets they address, talks regularly to a broad set of vendors and customers, and has a rigorous process for award selection all brings great credibility to the award. The award certainly has great meaning for us and I suspect this is also true for organizations who are thinking through what database to use for their next project. As a small company it’s always a challenge to get the word out about your products and this is particularly true when you’re in a space like NoSQL where there are lots of competing technologies. Membase wasn’t one of the first NoSQL products in the market, so it’s encouraging that our innovative work and early customer success is being recognized so quickly. We’re very proud that while IDC could have given the award to any of the many NoSQL contenders, they chose to give it to us.
We NorthScalers have been hard at work and are proud to release Membase Server Beta 4, our final Beta release ahead of our general availability release. Go and grab it here! In addition to support for 64-bit Windows, we think you'll be particularly excited by a major new feature in the release: memcached buckets! Introducing Memcached Buckets You now can create buckets in your Membase Server cluster that behave exactly like memcached, which means you can use Membase Server as a drop-in replacement for your existing memcached setup. In a single cluster you can now share the resources between memcached buckets and membase buckets. Let's look at the differences between memcached and membase bucket types: