IBM Invests In MySQL/Oracle Competitor
stoolpigeon writes "IBM has made a move to support open source RDBMS PostgreSQL by investing in EnterpriseDB, a company that supports PostgreSQL as well as selling their own proprietary extensions to the database product. IBM participated in a $10 million funding round, though the article doesn't say how much they invested. In the past EnterpriseDB has primarily advertised itself as an Oracle competitor, though the article says, 'Derek Rodner, EnterpriseDB's director of product strategy, explained that Postgres Plus 8.3 also adds in new application quick starts which are supposed to help with installation issues. They will also help in EnterpriseDB's battle against MySQL for open source database supremacy.'"
I completely agree. PostgreSQL used to be a bit slow, but for the last few years, there just isn't a reason to choose MySQL over PostgreSQL. PostgreSQL's license is certainly better and all the great features and SQL standards compliance makes it a no brainer, I think.
DB2 just doesn't scale down as well as some of the others so it doesn't get as much exposure to the masses, if you check out things like the TCP-H results you'll notice at the 10TB level DB2 is #1 and #3, it's typically used for very large databases running on IBM big iron. It's yet another IBM technology that kind of sits in the corner running some of the largest financial systems in the world without getting a lot of exposure.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
2002 called. It wants its MySQList retort back.
MySQL is no longer easier to use than PostgreSQL. PG is now availabe for Windows with a nice packaged msi installer. It is as easy or easier to install under Linux/BSD/other POSIX, and is (if you assume the same level of experience with both system) far easier to administer.
Not only that, MySQL's community consists of many newbies, which makes getting help on complex issues difficult. PG on the other hand has a vibrant community consisting of highly skilled DBAs and the PG core developers themselves. I've often had help from the PG core dev team members. Finding similarly skilled MySQL help is like trying to find Dodos in Manhattan.
I hate printers.
I love postgres- use it to handle millions of queries per day- but let's not kid ourselves: postgres replication in the form of slony blows. I have a master DB and it plublishes to a dozen read only databases. Managing that with slony just plain sucks. The simple fact is that setting up replication with mysql is dirt simple and that's part of why people use it.
I'm thinking of giving EnterpriseDB and their custom replication engine a try.
-sirket