4 ms·

* More active development * Slightly better performance IIRC * Not controlled by Oracle, who will likely kill off MySQL to promote their own database at some

* More active development * Slightly better performance IIRC * Not controlled by Oracle, who will likely kill off MySQL to promote their own database at some point in the not-too-distant future.

falcolas 12y ago
> * Not controlled by Oracle, who will likely kill off MySQL to promote their own database at some point in the not-too-distant future. To be fair, if they were going to do this, they wouldn't have invested the thousands of hours required to release 5.6, 5.7, Fabric, the mysql toolkit, etc. I've talked to the developers in person who work on MySQL, and they talk quite a bit about the future of MySQL. They have also acquired a number of MySQL based companies, and are committed to supporting them on MySQL.
- blueskin_ 12y ago
  It's also possible (although I considered less likely until around now) Oracle will simply cut off support, new versions, and patches in the future unless you pay, and recent work on it has only been to reassure the existing customer base into not switching to MariaDB/Percona/Postgres.
  - falcolas 12y ago
    Given how simple it is to drop in MariaDB/Percona Server without changes, this wouldn't be a terribly sound strategy. A better strategy is the one they currently use - selling support tools (like Enterprise Support, Enterprise Monitor, and Enterprise Backup) to support the development. It never ceases to amaze me how much people will pay for these tools and services to support a OSS product.
TylerE 12y ago
I don't think so, but I do expect them to monetize the hell out of it (e.g paid support). It's the Oracle for orgs that can't afford Oracle.
Roboprog 12y ago
My personal pet conspiracy theory is that Oracle needs to continue to propagate MySQL as the "first one's free", not-quite-good-enough database, so they can provide an easy migration from MySQL to Oracle when your app outgrows MySQL. I'm guessing there is a sizable slice of applications that would find PostgreSQL to be "good enough", and not need to buy Oracle subsequently. Perhaps that's just paranoid, and Oracle is running MySQL out of the goodness of its corporate heart?
- blueskin_ 12y ago
  >so they can provide an easy migration from MySQL to Oracle when your app outgrows MySQL. Based on personal experience, when databases hit that point, the logical next step is PostgreSQL if you're going to go through the pain of changing database engines. Or just do what $oldjob did and throw more and more resources at MySQL (256GB memory, anyone?).

* More active development * Slightly better performance IIRC * Not controlled by Oracle, who will likely kill off MySQL to promote their own database at some point in the not-too-distant future.

falcolas 12y ago

> * Not controlled by Oracle, who will likely kill off MySQL to promote their own database at some point in the not-too-distant future. To be fair, if they were going to do this, they wouldn't have invested the thousands of hours required to release 5.6, 5.7, Fabric, the mysql toolkit, etc. I've talked to the developers in person who work on MySQL, and they talk quite a bit about the future of MySQL. They have also acquired a number of MySQL based companies, and are committed to supporting them on MySQL.

blueskin_ 12y ago
It's also possible (although I considered less likely until around now) Oracle will simply cut off support, new versions, and patches in the future unless you pay, and recent work on it has only been to reassure the existing customer base into not switching to MariaDB/Percona/Postgres.
- falcolas 12y ago
  Given how simple it is to drop in MariaDB/Percona Server without changes, this wouldn't be a terribly sound strategy. A better strategy is the one they currently use - selling support tools (like Enterprise Support, Enterprise Monitor, and Enterprise Backup) to support the development. It never ceases to amaze me how much people will pay for these tools and services to support a OSS product.

TylerE 12y ago

I don't think so, but I do expect them to monetize the hell out of it (e.g paid support). It's the Oracle for orgs that can't afford Oracle.

Roboprog 12y ago

My personal pet conspiracy theory is that Oracle needs to continue to propagate MySQL as the "first one's free", not-quite-good-enough database, so they can provide an easy migration from MySQL to Oracle when your app outgrows MySQL. I'm guessing there is a sizable slice of applications that would find PostgreSQL to be "good enough", and not need to buy Oracle subsequently. Perhaps that's just paranoid, and Oracle is running MySQL out of the goodness of its corporate heart?

blueskin_ 12y ago
>so they can provide an easy migration from MySQL to Oracle when your app outgrows MySQL. Based on personal experience, when databases hit that point, the logical next step is PostgreSQL if you're going to go through the pain of changing database engines. Or just do what $oldjob did and throw more and more resources at MySQL (256GB memory, anyone?).