Fishpool

To content | To menu | To search

Tag - community

Entries feed - Comments feed

Thursday 20 November 2008

High-profile shutdowns and low-profile major updates...

Quite a day for negative articles on Google. I counted 10 articles on Lively shutting down, with the usual suspects gloating and cheering from the sidelines. Won't be joining that crowd, it's never fun to see someone's work being thrown out the window. I did want to relate that to a bigger picture, though.

This certainly won't be the last shutdown among the 100+ virtual worlds projects under work right now, and I wouldn't be surprised at all to see even higher-profile projects being canceled, either in the current financial bloodbath which curely will kill even some companies which 6 months earlier were entirely viable operations, or in the year to come when the business fails to materialize. Money's still being thrown in to the game at pretty amazing rate, and there's just not enough experience to go around to make all these projects work.

And that's because at the end of the day, this business is not about the brand, the IP, the coolest technology, or even the best user experience. Instead, this is about being able to nurture a community, co-operate with it to develop something which no one knows where it will ultimately end up at, and to be on the pulse of what's going on, every minute of every day. I know it's easy to forget that, with the allure of focusing on the superficial, easy to analyze product features, APIs, and so on.

We've certainly learned that the hard way ourselves - it's not like we've always kept our eye on the ball either. Still, you only need to be right most of the time, listen carefully, and not miss where you need to correct yourself. It's now been roughly a year since we launched a significant refresh to Habbo that put the service on the track its been on since, after what can be described only as a pretty horrible summer 2007 for us.

That was 12 months and 11 upgrades ago, though. Yesterday we launched what's internally called release 28 of Habbo in UK. The most exciting features of it haven't yet been turned on, as we're preparing yet another global roll-out to begin next week. This is an important release to us, possibly as important as the one made a year ago, as it'll change the economic and reward models of the community forever. I hope we got it right on this one. If we did, it's going to be an amazing Xmas, for us and for all the Habbos. If not, well, then we'll need to scramble a bit to make it fun anyhow. But that's what we're good at.

Tuesday 22 April 2008

MySQL Users Conference followup and MySQL's business model

Last week saw MySQL User Conference 2008 in Santa Clara, but I was not able to make time for it this year either. However, in the wake of Sun's acquisition of MySQL, it was very interesting to follow what was going on. A few things that caught my attention:

MySQL 5.1 is nearing General Availability and an interesting storage engine plugin ecosystem starts to emerge. It's this latter, but related event that I see as the first real sign of validation for MySQL's long-ago chosen path of pluggable storage systems instead of focused effort on making one good general-use engine.

Oracle/Innobase announced InnoDB Plugin for MySQL 5.1, which much-awaited features which promise a great deal of help for daily management headaches. More than that, InnoDB Plugin's release under GPL lifts quite a lot of the concern I'm sure many users like us have had about the future viability of InnoDB as MySQL storage engine.

A couple of data warehousing solutions are launched, also based on MySQL 5.1 -- Infobright is one I've already researched somewhat (looks very interesting, as soon as a few current limitations are lifted), Kickfire I know nothing about right now but would love to learn more of.

There's a huge amount of coverage graciously provided by Baron Schwartz that I have yet to fully browse through.

A few remarks by Mårten Mickos regarding MySQL's business model seem to have kicked up a bit of a sandstorm. I don't really understand why; I read these to just verify that the direction MySQL took last year is to continue this year as well. I don't see any major changes here regarding the licensing structure, software availability, or support models. Frankly, it seems like yet another case of Slashdot readers not reading, let alone understanding, what they're protesting against, and press following up on the noise.

I do understand the critique made against MySQL's chosen model, though. In fact, I went on record last September to say that I understand that critique. I still see the same issues here. I believe we represent a fairly common profile of a MySQL Enterprise customer in that what we want from it is not the bleeding-edge functionality but a stable, well-tested product that we can expect to get help for if something does go wrong. We don't see great value in having access to a version of software that isn't generally available to "less advanced" or more adventurous users for free in a community version. In fact, we see it as a negative that such functionality exists, because it hasn't received the community testing, feedback and improvements that makes great open source software as good as it is. While new functionality is interesting, and we're trying to spend time getting familiar with new stuff in order to use it in production later, it simply isn't prudent to put business-critical data in a system that hasn't received real-world testing by as large a community as possible (unless you have no other alternative, and then you takes your chances).

Yet it seems to me that this is essentially what Sun/MySQL continue to propose for the Enterprise customers by delivering "value add" functionality in a special version of the server or plugins to it, possibly in a closed-source form that further reduces transparency and introduces risk. Mårten, I'd prefer it to be otherwise. How can I help you change your mind about this?

Friday 21 September 2007

MySQL Community vs Enterprise tension

I probably don't spend quite enough time following progress around MySQL considering how critical the product is to us. I'd like to consider it part of the infrastructure in a way I treat Red Hat Enterprise Linux, ie something I can trust to make good progress and follow up on a quarterly basis. Naturally we have people who watch both much more closely, but my time simply should, and pretty much is, spent doing something else.

However, it seems MySQL really demands a bit more attention right now. Today I went and read Jeremy Cole's opinion about MySQL Community (a failure), and I have to say I agree on many of the points. MySQL simply has not yet found a model that works as well as that of Red Hat's Fedora vs Enterprise Linux - that is, really giving the Community edition to the community to direct, and using the Enterprise edition as a platform for enterprises to depend on.

I feel the fundamental problem really is quite simple; as long as MySQL maintains the community edition (both binaries AND the source tree) themselves, and don't let the community integrate features to it on a timely basis, the model will not function, not even to their paying customers (us included). However, if they reverse this particular point from the current status-quo, all of the other benefits are inevitable.

The comparison to Fedora and RHEL is rather obvious, despite the distribution vs single product differences. Fedora is a great community Linux distribution with the latest-and-greatest features integrated to it on a very timely fashion. Not even Ubuntu can really compete with Fedora in terms of features. However, what Fedora gives up to reach this is a certain amount of polish and reliability. I will happily use Fedora as a personal platform, because of the latest features, but I would not pretend to run a stable system on top of it. For that, I'll rather choose something a bit more mature, that has proven itself in the community and received further QA ahead of commercial release. This is RHEL, and this is what the MySQL Enterprise should be. A version that, when it's released, I shouldn't have to hesitate to install on a new production server.

I also today learned about the Dorsal Source MySQL community release. Now this looks like something MySQL Community release probably should be like. I'll have to give it a test round and see what's up.

Update: Baron Schwartz describes a MySQL Enterprise that I would have far less trouble using than the existing one..