The state of MySQL forks: co-operating without co-operating
The state of MySQL forks: co-operating without co-operating
Dec 6, 2010, 22 :02 UTC (0 Talkback[s]) (622 reads)
"Giuseppe "The Data Charmer" Maxia recently posted his take on the MySQL forks. I had been pondering whether to do the same, and seeing that what I planned to write will nicely complement Giuseppe's article, I was inspired to follow him into the same topic. Note that last Spring I created a Map of MySQL forks in preparation for Monty's keynote at the MySQL user conference. So let's see how things have evolved. I'll look into MySQL ecosystem as a whole and the forks separately.
"The post is long, but the key takeaway is that despite the challenges, the combined development seen in the MySQL ecosystem is probably stronger than ever, the current situation is hard for an outsider to grasp but manageable, and if a few more obstacles can be overcome, we are looking into a very bright future indeed. There are more than 100 engineers (how much more?) working full time on the mysql code base (including both developers, QA, build engineers...). This development effort is an order of magnitude higher than other open source databases I'm aware of, in particular PostgreSQL and Drizzle. Often the open source project with most momentum and mass will come out as the winner, no matter what challenges it may seemingly be facing, and this is the case with MySQL too. Oracle's MySQL"
Complete Story
Related Stories:
The LXer Interview: Ulf Sandberg, CEO of SkySQL(Dec 06, 2010)
MySQL vs. PostgreSQL, Part 1: Table Organization(Dec 01, 2010)
Comparing MySQL and Postgres 9.0 Replication(Nov 18, 2010)
MySQL Hotbackups with XtraBackup(Nov 16, 2010)
A report from OpenSQLCamp(Nov 16, 2010)
Can Firebird gain against MySQL? (Nov 15, 2010)
