"In response, companies that are behind MySQL are coming together. Rather than continuing with things as they are, these companies recognize that developing a future path for MySQL is essential. What this will lead to will depend on decisions outside the community. Will this act as a spur for a fork of MySQL that has community support, similar to PostgreSQL? Or will this lead to MySQL moving away from the control of a single vendor, as has been the case since it was founded?"
"MySQL has a huge community around it, and there is a lot of passion around what the future holds for the database. The challenge is how to direct that passion and get MySQL back to where it should be. MySQL is a great database that makes it easy to implement and run applications, and it is a useful option where PostgreSQL is not a good fit or overkill for an application deployment."
Companies behind MySQL are organizing to develop a future path for the database, with outcomes depending on external decisions. Possibilities include a community-supported fork similar to PostgreSQL or MySQL becoming less controlled by a single vendor. MySQL remains a valid open source database choice for developers, supported by a large, passionate community. The challenge is channeling that passion to restore MySQL's position where appropriate. MySQL simplifies application implementation and deployment and can be preferable when PostgreSQL is unsuitable or excessive. Community events and the Foundation for MySQL Slack channel offer avenues for participation to help shape MySQL's future.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]