Linked by snydeq on Thu 21st May 2009 22:55 UTC
Databases Fatal Exception's Neil McAllister questions the effect recent developments in the MySQL community will have on MySQL's future in the wake of Oracle's acquisition of Sun. Even before Oracle announced its buyout, there were signs of strain within the MySQL community, with key MySQL employees exiting and forks of the MySQL codebase arising, including Widenius' MariaDB.
Permalink for comment 364985
To read all comments associated with this story, please click here.
RE[2]: not an expert
by werpu on Fri 22nd May 2009 16:47 UTC in reply to "RE: not an expert"
Member since:

"I am not an expert but there must be reasons why people chose MySQL over Postgres.

Years ago there used to be a significant performance gap(in MySQLs favor) between MySQL and Postgres when under the sort of loads often found with web sites. The admin tools for MySQL used to be better and easier to handle. Also a great many third party applications and libraries used to be MySQL only and require a great deal of hacking to get working with postgres.
The problem I saw was that the performance was only there due to the reason the MySQL guys left out transactions for a reason. They could not pull of their own transactional storage.
Exactly this made me suspicious about MySQL in general before even having used it. Then shouting out left and right that no one needs transactions anyway, because they could not pull it off did not help me in my confidence using it!

The funny thing is, as soon as they added a transactional storage backend the speed went down big ways especially if you used it in classical relational situations with joins over several tables and parallel access!

On the other hand Postgres devlivered transactions out of the box, and improved their performance and nowadays is in the same league as MySQL in its isam implementations while handling parallel loads way better, while MySQL itself still has not transactional storage mechanism of its own (well not it has now that everything is under the Oracle umbrella)

Non of these limitations hold true and more, but the result of all of this is that there are a lot more people and projects that use MySQL for historical reasons and see no compelling reason to change. Even when starting a new project many people will go with what they know.

I´d say the biggest problem why everyone adapted MySQL was, the media hype and the close tie in the LAMP stack between PHP and MySQL. But I see a load of shift recently. The kids from back then have grown up and now know better about databases. The raving from a few years back is gone and a load of MySQL users already also use alternatives and mygrate. I think the reason why MySQL still is as strong as it is is mostly legacy applications which are too costly to be migrated to another DBMS, and for simply webapps MySQL often is fine enough (if you dont run into buggy UTF-8 implementations like I did in version 4)

Reply Parent Score: 2