● Beta — KubeEra is in active development. Profiles are live; AI-perception measurement and reviews are still being built.
KubeEra
M

MySQL

App Definition & Delivery
Open source · NOASSERTION

MySQL is an open-source relational database management system (RDBMS) built in C++.

updated 2026-07-01

What it is

MySQL is an open-source relational database management system (RDBMS) built in C++. It's one of the most widely deployed databases in the world, powering everything from WordPress blogs to large-scale web applications at companies like Meta, Booking.com, and countless SaaS backends. Full product description: not publicly available from the data provided here, but functionally it's a SQL-based, ACID-compliant (with InnoDB) database engine supporting replication, partitioning, and clustering.

Who builds it and why

MySQL is owned and primarily developed by Oracle, following its acquisition of Sun Microsystems (which had acquired MySQL AB) in 2010. Oracle funds the core engineering team and drives the roadmap, storage engine improvements (InnoDB), and enterprise features. The GitHub mirror shows 698 contributors, but in practice the vast majority of commits come from Oracle-employed engineers — community contributions exist but don't drive core direction the way they might in a foundation-governed project. Founded: not publicly available in this dataset, though MySQL's public history dates to 1995.

Production readiness signal

  • 12,321 GitHub stars, 698 contributors — solid numbers, though notably lower than what you'd expect for a database this dominant, which suggests the primary development activity or star count is tracked elsewhere (Oracle's Bitbucket/internal mirrors, or a different GitHub org) rather than fully reflected in this repo.
  • Last commit: 2026-06-18 — actively maintained, no signs of abandonment.
  • Latest release: not publicly available in this data, but MySQL ships regular point releases (8.x line) on a predictable cadence with LTS-style innovation/LTS release tracks since 8.0.
  • License: listed as NOASSERTION, which typically means the scanning tool couldn't cleanly parse a single SPDX license. In reality, MySQL is dual-licensed: GPLv2 for the community edition, with a commercial license available from Oracle for embedding MySQL in proprietary products without GPL obligations. Know which one applies to your use case before you ship.
  • CNCF maturity: not applicable — MySQL isn't a CNCF project.

Bottom line: this is battle-tested infrastructure with decades of production hours behind it. The operational risk isn't "will it work," it's "do you understand replication topology, backup strategy, and failover well enough to run it at your scale."

Who should use this

  • Teams needing a proven, well-documented relational database with a massive hiring pool of engineers who already know it.
  • Applications with read-heavy workloads that benefit from mature replication support.
  • Organizations already invested in the MySQL ecosystem (ORMs, migration tools, monitoring integrations) where switching costs outweigh marginal gains elsewhere.
  • Teams that want commercial support as an option (Oracle, Percona, or managed cloud offerings) rather than pure community support.

Who should NOT use this

  • Teams needing native horizontal write scalability without bolting on external sharding — look elsewhere before you build that yourself.
  • Heavy JSON/document-first workloads where a document database fits the access pattern better than relational tables.
  • Analytics/OLAP workloads — MySQL is OLTP-first; you'll fight it for large aggregate queries at scale.
  • Anyone uncomfortable with Oracle's stewardship and the GPL/commercial dual-license model — if that's a legal or philosophical blocker, pick a project with unambiguous licensing and independent governance.
  • Teams wanting cutting-edge SQL feature parity with Postgres (window functions history, advanced indexing, extensions) — Postgres has generally led on feature depth.

Alternatives

  • PostgreSQL — more extensible, stronger standards compliance, no corporate single-vendor control; the default recommendation for new projects today.
  • MariaDB — MySQL-compatible fork born specifically to escape Oracle's control, community-governed, drop-in for most MySQL workloads.
  • CockroachDB — if you need real horizontal scalability and distributed consistency without manual sharding, at the cost of operational complexity and licensing considerations of its own.

Pricing

Community Edition is free and open source under GPLv2. Oracle also sells MySQL Enterprise Edition (support, additional security/monitoring tooling, backup) and a commercial license for embedding MySQL without GPL obligations. Cloud-managed versions (AWS RDS, Azure Database for MySQL, GCP Cloud SQL) charge on usual compute/storage/IO pricing models — check your provider directly, exact figures not publicly available here.

Frequently asked

What is MySQL?+
MySQL is an open-source relational database management system (RDBMS) built in C++. It's one of the most widely deployed databases in the world, powering everything from WordPress blogs to large-scale web applications at companies like Meta, Booking.com, and countless SaaS backends.
Who builds MySQL?+
MySQL is owned and primarily developed by Oracle, following its acquisition of Sun Microsystems (which had acquired MySQL AB) in 2010. Oracle funds the core engineering team and drives the roadmap, storage engine improvements (InnoDB), and enterprise features.
Is MySQL production ready?+
12,321 GitHub stars, 698 contributors — solid numbers, though notably lower than what you'd expect for a database this dominant, which suggests the primary development activity or star count is tracked elsewhere (Oracle's Bitbucket/internal mirrors, or a different GitHub org) rather than fully reflected in this repo.
Who should use MySQL?+
Teams needing a proven, well-documented relational database with a massive hiring pool of engineers who already know it. Applications with read-heavy workloads that benefit from mature replication support.
Who should not use MySQL?+
Teams needing native horizontal write scalability without bolting on external sharding — look elsewhere before you build that yourself. Heavy JSON/document-first workloads where a document database fits the access pattern better than relational tables.
What are the alternatives to MySQL?+
PostgreSQL — more extensible, stronger standards compliance, no corporate single-vendor control; the default recommendation for new projects today. MariaDB — MySQL-compatible fork born specifically to escape Oracle's control, community-governed, drop-in for most MySQL workloads.
How much does MySQL cost?+
Community Edition is free and open source under GPLv2. Oracle also sells MySQL Enterprise Edition (support, additional security/monitoring tooling, backup) and a commercial license for embedding MySQL without GPL obligations.