As we set out to help the MySQL ecosystem assert greater independence from Oracle by establishing a vendor-neutral industry association, we had to confront a deceptively simple question:
What exactly is the MySQL ecosystem?
There are many views on this question.
Some argue it should revolve strictly around the MySQL brand—meaning MariaDB would be excluded. Others believe it should be defined by codebase lineage—therefore ruling out systems like TiDB. Still others insist it must center exclusively on open-source software, which would exclude offerings such as AWS Aurora for MySQL.
We believe this kind of exclusivity is counterproductive. It shifts the focus to boundaries instead of outcomes.
What truly matters are MySQL users: the application builders and the operations professionals who rely on the ecosystem to deliver real systems at scale.
Any database solution or tool that has meaningful MySQL compatibility should be welcome.
Accordingly, we believe cloud vendors offering MySQL-compatible databases should be invited to participate—regardless of whether their solutions are built directly on the MySQL codebase.
MariaDB remains a practical alternative for many MySQL users and introduces unique capabilities not available elsewhere.
Distributed solutions such as TiDB, PlanetScale, and Vitess enable scaling far beyond the limits of a single server, making them highly relevant for modern applications.
In the end, we see it simply:
If your software or service helps MySQL users succeed, you are part of the MySQL ecosystem.
About the Author
Peter ZaitsevPeter managed the High Performance Group within MySQL until 2006, when he founded Percona. Peter has a Master's Degree in Computer Science and is an expert in database kernels, computer hardware, and application scaling.
