The future of MySQL ?!
Submitted by Chandrashekar Babu on April 22, 2009 - 2:05pm.
::
As murky as it turned out to be, the latest news has it that Oracle is currently signing up on acquisition of Sun Microsystems (who currently owns OpenOffice and MySQL).
The real problem could be the future of MySQL. The way I see it, MySQL's technology/innovation died already after Sun's acquisition. Now, Oracle would kill the brand too, and perform the last rites.
We now have just "one" database for the large-scale enterprise - Oracle Database Server (well, there's DB2, Informix and MS SQL Server too - but they are not that significant in the Web development market). MySQL as a brand will be missed. Let's hope that the core MySQL developers come out with something better (out of their MySQL fork).
We miss you MySQL!
//We now have just "one" database for the large-scale enterprise - Oracle Database Server (well, there's DB2, Informix and MS SQL Server too - but they are not that significant in the Web development market).//
What about PostgreSQL?
It is open source and used for web applications.
PostgreSQL is a robust and more feature complete database in comparison with MySQL/MariaDB. It is best suited for replacing Oracle/DB2/Informix on enterprise applications.
What PostgreSQL currently lacks is a robust and well-supported distributed/replicated cluster. But there are workarounds for that too.
However, PostgreSQL has a much stricter implementation of SQL and RDBMS rules, unlike MySQL that relaxes many rules for the sake of practicality (zero dates, weak data types, delayed inserts, SET and ENUM data types and so on). These features can sometimes be the design factors for choosing databases catering to web applications.
Overall, PostgreSQL is a good replacement for more enterprise-grade SQL databases.
Regards,
Chandrashekar.