Recently we were approached by some of our users questioning our assessment/rating of MySQL versus PostgreSQL. Currently MySQL is rated with four stars for Enterprise Readiness, while PostgreSQL only shows three. All the other ratings (functionality, maturity, community, trend) are the same otherwise. This seems to be a good occasion to talk a bit about our rating criteria and the way we apply them. Also, we were having quite a bit of a debate in the newly formed EOS Advisory and Expert Board on this same topic, so it’s good to share some of the findings.
So, here’s how we describe the Enterprise Readiness rating on this site:
On the basis of the other criteria and additional experiences as well as further product characteristics (e.g. how easily a base technology be introduced can into the typical enterprise, how reactive the community is, how easily a product can be integrated in commonly-found enterprise IT environments, or how well does the product support open standards) the Enterprise Readiness Rating (aka “Optaros rating”) indicator is consolidated. This rating describes how capable an open source product is to cope with the needs and requirements of midsize and large enterprises and organizations. The EOS Directory does not list products that do not at least meet the 1-star rating.
To go a bit more in detail there are a number of aspects that influence our assessment of Enterprise Readiness, beyond of what is coming from the other rating factors:
- Popularity, market reach, distribution power, public awareness, typical ranking in top x lists:
Clearly here MySQL seems to outperform PostgreSQL. If you google for example for the two technologies you will see that you have approx. 10 times more hits for MySQL than for PostgreSQL. Same effect when you look at Google Trend.
Asking a typical enterprise architect what open source databases come to his mind, he usually will mention MySQL first. Even on EOS Directory MySQL is much more popular (number of page hits) than PostgreSQL.
- Availability and quality of professional services and consulting:
How easiy is it to find a training for MySQL versus PostgreSQL? How many potential partners can an Enterprise find to help with tuning, integration, support, etc.? Also here MySQL seems to be ahead of PostgreSQL. But with EnterpriseDB, Fujitsu, CommandPrompt, 2ndQuadrant, Cybertec and other firms, Enterprises should be able to find good help for PostgreSQL also. So, no real advantages of one against the other.
- Adoption in the market (byEnterprises as well as SW vendors):
MySQL has been very successful in partnering with all kinds of SW vendors (not only Open Source product companies). This results into a much higher adoption of MySQL in both the software vendors and consequently their end customer. Even on SourceForge MySQL is referenced by more than 7′000 other projects, while PostgreSQL is being mentioned by less than 1′000. Independently many Enterprises have established MySQL clearly as their second database standard (after Oracle or IBM), this is less often the case with PostgreSQL. So in terms of adoption MySQL takes the lead again.
- Enterprise specific atribute, features, extensions and requirements:
Here we look whether MySQL offers better/more migration tools for example, whether it’s easier to manage with the typical enterprise tools already in place, etc. MySQL may have a bit of an advantage here, but not by much.
- Enterprise culture orientation:
Is MySQL easier to buy for Enterprises than PostgreSQL? Does the support of Sun (and now Oracle) help to make it easier to evaluate and consume? Probably yes, but with the disadvantage of being less “open source”.
Now there’s a lot more to say about the two technologies of course. There are some known problems with MySQL that ask for workarounds, similar issues probably exist around PostgreSQL. There are open source projects that clearly recommend PostgreSQL over MySQL, e.g. Jackrabbit or Django. These things however should rather influence the “maturity” rating than the Enterprise Readiness. So if we keep the top rating for Maturity for both technologies we can’t make this a differencing factor in Enterprise Readiness. The same is true with other aspects such as the validity of the community or the availability of features.
There have been discussions in the EOS Advisory and Expert Board to automate more of the rating process and base it on available data. This may be well the way to go for the future, but in my eyes it’s exactly these discussions and real world experiences that make the EOS Enterprise Readiness rating so powerful.
Now, to come back to MySQL and PostgreSQL, should we downgrade MySQL to three stars, upgrade PostgreSQL to four stars or leave it as it is today? Stay tuned, we will make our decisions in the coming days 
And anyway, both are good and widely used technologies. The difference isn’t big, but may be somewhat prestigious. Join the discussion!