Stop using MySQL in 2026, it is not true open source

Summary

The article argues for abandoning MySQL in favor of MariaDB due to concerns about MySQL's open-source status and Oracle's stewardship. It cites declining development activity, security issues, and feature deprecation as reasons for the recommendation. The author suggests MariaDB as a straightforward alternative, especially for LAMP stack applications.

Key Takeaways

1. MySQL's open-source status is questionable under Oracle, with development happening behind closed doors and limited community involvement.
2. MariaDB is presented as a true open-source alternative with transparent development and community contributions.
3. Migrating from MySQL to MariaDB is straightforward for many applications, making it a viable option for users concerned about MySQL's future.

Statement Breakdown

• Claimed Facts: 50% of statements the article presents as facts
• Opinions: 30% of statements classified as editorial or subjective
• Claims: 20% of statements surfaced for additional reader evaluation

Credibility & Bias Reasoning

Credibility assessment: The article presents a clear argument with supporting evidence, including specific examples and references to industry experts. However, the author's personal experiences and opinions are heavily intertwined with factual claims, which introduces potential bias. The article also relies on anecdotal evidence and interpretations of events, which could be subjective.

Bias assessment: Pro-MariaDB/Open-Source Advocacy. The article strongly advocates for switching from MySQL to MariaDB, framing MySQL's current state as a decline due to Oracle's stewardship. It consistently portrays MariaDB as the superior open-source alternative, highlighting its community-driven development and transparency. This clear preference and promotion of MariaDB indicates a significant bias.

Note: This article contains a strong bias towards MariaDB and presents a critical view of MySQL under Oracle's management. Readers should consider alternative perspectives and verify claims independently.

Credibility flag: Consider Perspective

Claimed Facts (7)

• This is presented as an observable fact based on git commit history.
• This is a historical event that can be verified.
• This is a statement about the licensing and development practices.
• This refers to specific release dates and types.
• This refers to a reported event about workforce reduction.
• This is a quantifiable statement about published CVEs.
• This is a statistic about WordPress usage.

Opinions (6)

• This is a subjective assessment of Oracle's trustworthiness.
• This is a personal anecdote about developer experiences.
• This is an interpretation of how open source is implemented.
• This expresses the author's fear and is subjective.
• This is a comparative statement about security issue handling.
• This is a subjective assessment of Oracle's motivations.

Claims (6)

• This is an oversimplified generalization.
• This is an emotional appeal to the reader's values.
• This is a vague statement without specific evidence.
• This is a subjective assessment of technical deterioration.
• This is an interpretation of Oracle's motives without concrete proof.
• This relies on anecdotal evidence from unverified sources.

Key Sources

• Otto Kekäläinen — Author
• Oracle — Company
• Michael Widenius — Original MySQL author
• Amazon Web Services — Employer of the author
• Mark Callaghan — MySQL performance expert
• Peter Zaitsev — Percona