Following my talk at Jazoon (which I covered in my earlier blog), I had a whirlwind trip to five Java User Groups (JUGs) in Europe and the Pacific Northwest. I would like to thank Gerd Cestan and the Stuttgart JUG, Antonoio Goncalves and the entire committee at Paris JUG, Nimret Sandhu and the Seattle JUG, Manfred Moser and the Victoria JUG and Darren Gibbons and Sam Cirka and the Vancouver JUG for hosting me.
It’s been a busy few weeks since CouchConf San Francisco, where we announced and demo’d the developer preview of Couchbase Server 2.0, which integrates Apache CouchDB, Membase and Memcached into a single, powerful NoSQL database solution.
We just finished an update to the developer preview and it is now available. Be sure to download the latest version and let us know what you think.
Membase is "on the wire" compatible with any memcached server if you connect to the standard memcached port (registered by myself back in 2009), so that you should should be able to access membase with any "memcapable" client. Backing this port is our membase proxy named moxi, and behind the scene it will do SASL authentication and proxy your requests to the correct membase server containing the item you want.
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.
In the previous blog post I described the engine initialization and destruction. This blog post will cover the memory allocation model in the engine interface.
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.
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:
Memcached security is a hot topic since the sensepost guys released go-derper at blackhat.
The presentation was pretty good and informative, but it seems like the hype around it has left a bunch of people confused. Although much of this was covered in the presentation, it needs to be restated as much as possible.