Oracle’s 2025 MySQL Layoffs: What It Means for Open‑Source Databases

Oracle announced a large‑scale global layoff in September 2025, affecting multiple business units, with the MySQL core development team hit hardest.

Around September 11, roughly 70 core MySQL engineers—including those responsible for performance optimization, feature development, and community support—were dismissed.

MySQL founder Michael Widenius responded on social media, saying he had "anticipated Oracle’s move" but was still "very sad" about the actual event.

He noted that since Oracle’s 2010 acquisition of Sun Microsystems and takeover of MySQL, the team has faced shrinking resources and strategic shifts.

This is not the first time Oracle’s commercial strategies have raised open‑source community concerns; similar worries emerged after the 2010 acquisition, fearing MySQL could be marginalized or closed.

In response, Widenius led a group of core developers to create MariaDB, a fully compatible and more firmly open‑source fork.

Now, a former MySQL engineer claims Oracle is redirecting resources toward Heatwave, its cloud‑native analytics database, and heavily investing in AI features.

This aligns with the broader industry trend of tech giants bolstering AI, but from the community’s perspective, the MySQL community edition may be gradually "left behind".

Percona founder Peter Zaitsev emphasized that the layoffs are not an isolated incident but a signal of Oracle’s overall strategic shift.

He warned that while MySQL will continue to receive short‑term maintenance, long‑term innovation, performance improvements, and community support could diminish significantly.

MySQL, a cornerstone of the LAMP stack, powered the explosive growth of early internet giants like Twitter and Facebook, and remains the world’s most popular open‑source relational database, especially in large‑scale internet services and traditional enterprises.

Many recall the "MySQL defense war" when Oracle acquired Sun, with open‑source leaders like Richard Stallman warning that MySQL might lose vitality under a commercial‑software‑focused owner.

Although the EU approved the acquisition with conditions to maintain MySQL’s open‑source status, those commitments now appear vague.

Similar patterns have occurred elsewhere, such as IBM’s acquisition of Red Hat and Microsoft’s purchase of GitHub, where open‑source projects faced strategic uncertainty.

For developers, a potential decline of MySQL directly affects project maintenance and future technology choices.

Fortunately, MySQL’s strong open‑source foundation and widespread market adoption mean that, even with reduced Oracle investment, the community and third‑party companies like Percona and MariaDB will continue to provide support.

MariaDB, the most well‑known MySQL fork, has already become a seamless replacement in many scenarios, offering compatibility, performance enhancements, and better support for cloud‑native architectures.

This layoff not only reflects a corporate strategic adjustment but also reminds us that in a vendor‑driven open‑source world, project destinies are often dictated by capital and commercial interests rather than the community.

If a flagship project like MySQL can face resource withdrawal, the sustainability of smaller open‑source projects becomes a pressing question.

The tech world has no immutable products, yet the spirit of open source lies in collaboration and sustainability.

Perhaps this event serves as a catalyst for developers to recognize the risks of over‑reliance on a single vendor and to embrace a truly community‑driven, multi‑vendor open‑source ecosystem.

According to leaked internal Oracle sources, severance packages sometimes follow an N+1 model or include an additional six months’ pay.