I read Tokyo Cabinet: Beyond Key-Value Store today from one of the news sites, and it reminded me of Brian’s hack on Tokyo Cabinet == Tokyo Engine. Looking at TokyoEngine in Brian’s Mercurial repository, there have been no updates in over a year. Is anyone planning on taking up development of this? Tokyo Cabinet looks really interesting, and Brian has already started the enabling of making it a MySQL engine.

…

Open-Xchange raises Series B funding. The FSF enables Wikimedia’s potential move to the Creative Commons Attribution-ShareAlike 3.0 license. The “Bilski” decision and software patents. Mindtouch reports revenue growth. And more.

Press releases
Open-Xchange Closes Series B Venture Funding of $9 Million Open-Xchange

OASIS Members Form Committee to Advance Interoperability and Conformance of OpenDocument Format (ODF) Applications OASIS

FSF Releases New Version of GNU Free Documentation License Free Software Foundation

Federal Court Issues “Bilski” Decision Software Freedom …

I’ve been following the Drizzle project with some interest. There’s a lot to like about it. But you know what I like most about the project?

No dual licensing. Just plain GPL, version 2.

I personally think this is the foundation for why people are empowered, why there is excitement, why there is progress, [...]

Brian Aker was at the Sun booth today, in a premier slot, where there must have been about 50-60 people, huddled around, to listen to him talk about Drizzle. The project motivations, what’s behind it, what its not aimed to be, and so much more. Check the video out (21 minutes long)!

The Birds of a Feather (BoF) session in the night, was well attended, and there was lots of large discussion on what’s next. I think the important message to take away is that Drizzle doesn’t aim to be MySQL, and there are no plans to “merge” things back (fixes where the code-base is shared though, might make sense). Its also important that the design is for the future, i.e. multi-core machines. It was great to see Brian say that this …

Interested in MySQL? Drizzle? How the Sun acquisition is going for MySQL? Listen to Brian, Monty, and Tim speak about this, at the OSCON panel. Watch the video, its 20+ minutes, it starts off a bit shaky (oops), but I’m mostly happy with the rest. Enjoy.

When Sun acquired MySQL and announced that it would invest the resources necessary to position the open source database for mission-critical deployments, I think everyone assumed that the database would eventually become bigger and heavier.

Few would have predicted that we would also see a project that would make the database smaller and lighter, but that is exactly what Drizzle, a new project from Sun’s MySQL director of architecture Brian Aker, is all about.

Drizzle is taking a back-to-the-drawing-board approach to refactoring MySQL by ripping out much of the additional enterprise functionality that has gone into it since version 4.1 and focusing on the demands of a core set of applications.

As Brian …

At OSCON, Brian and Dormando gave their ever famous talk, Memcached and MySQL: Everything You Need To Know. I didn’t attend the tutorial, but they assured me it was similar to what was given at the MySQL Conference 2008 (everything, but the very nice buttons dormando was giving out with the memcached logo!). Great, because not only is memcached hot, but I have notes from their talk: Memcached and MySQL tutorial.

Interestingly enough (and this didn’t happen at OSCON), …

Day two of the conference was a little disappointing, as far as sessions went. There were several time blocks where I simply wasn’t interested in any of the sessions. Instead, I went to the expo hall and tried to pry straight answers out of sly salespeople. Here’s what I attended.

Paying It Forward: Harnessing the MySQL Contributory Resources

This was a talk focused on how MySQL has made it possible for community members to contribute to MySQL. There was quite a bit of talk about IRC channels, mailing lists, and the like. However, the talk gave short shrift to how MySQL plans to become truly open source (in terms of its development model, not its license). I think there was basically nothing to talk about there. I had a good conversation about some of my concerns with the speaker and some others from MySQL right afterwards.

There was basically nobody there — I didn’t count, but I’d say maybe 10 or 12 people. I …

I know I’m a little late to the discussion, but Brian Aker posted a thought-provoking piece on the imminent death of MySQL replication to scale reads.  His premise is that memcached is so cool and scales so much better, that read replication scaling is going to become a think of the past.  Other MySQL community people, like Arjen and Farhan, chimed in too.

Now, I love memcached.  We use it as a vital layer in our datacenters, and we couldn’t live without it.  But it’s not a total solution to all …

I've decided to start replacing L with GL in acronyms where L supposedly stands for Linux.

I'm not a big user of acronyms, because I think they are exclusionist and they obscure, rather than revealing. (This wouldn't matter if I wrote for people who already knew what I meant and agreed with me, but that's a waste of time). However, LAMP is one that I've probably used a few times, without thinking that it is supposed to stand for Linux, Apache, MySQL, and PHP/Perl/Python. In fact, it doesn't refer to Linux, it refers to GNU/Linux. Therefore, it should be GLAMP.

Why does this matter? I try not to say Linux, unless I'm referring to a kernel, because a kernel is not an operating system. I try to be pretty careful about saying GNU/Linux when I'm talking about an operating system. An exception is a recruiting event yesterday at the University of …