MySQL review

MySQL is a relational database platform, not an application framework or a standalone hosted API. The Community Edition is the free, GPL option; paid offerings include Standard, Enterprise and Cluster editions. HeatWave is a cloud service that combines transactions with lakehouse-scale analytics, while MySQL AI provides machine learning and generative AI capabilities.

In an application stack, MySQL stores and serves structured data for application code and other database clients. Teams can choose a Community deployment or paid server licences, and organizations building products can use MySQL as an embedded database through OEM/ISV licensing. HeatWave is the cloud offering for teams that want analytics and transaction processing in one service. The homepage also describes MySQL Cluster for web, cloud and communications services. These offerings are not one interchangeable deployment: decide whether you need a self-managed database, an enterprise licence, a cluster deployment or HeatWave before comparing costs and operating requirements.

MySQL is a SQL database, rather than a REST API or a library that you call directly from application code. Your application needs a MySQL-compatible client connection to issue queries; check the vendor's documentation for the supported connection protocols, language drivers, SDKs and command-line tools for your stack. The homepage promotes Community Early Access downloads for previewing and evaluating upcoming Community Edition builds, and links to MySQL Reference Architectures for security and high availability.

The product pages describe HeatWave as a cloud service, MySQL AI as integrated machine learning and generative AI, and Enterprise Edition as including management tools and technical support. They do not establish a specific SDK or language integration surface in the homepage text. Confirm client-library support and version compatibility in the vendor's docs before selecting a language runtime or deployment. The homepage also lists a webinar introducing MySQL 9.7 LTS, but teams should check the release and download documentation for current version details.

MySQL Community Edition is free under GPL. Its socket and seat limits are not published, so confirm applicable terms before using it in production. Paid list prices are annual per server, not published monthly subscriptions: Standard Edition costs $2,140 per year for 1–4 sockets or $4,280 for 5+ sockets. Enterprise Edition costs $5,350 or $10,700 per year for those server sizes, respectively, and includes a 30-day trial.

MySQL Cluster Carrier Grade Edition costs $10,700 per year for a 1–4-socket server; the 5+ socket price is not published. Classic Edition is available only through OEM/embedded licensing, with price not published. The pricing page lists no add-ons. The bill scales by licensed server and socket tier, rather than a published request, seat or compute meter. Budget for annual licence costs as servers move into a higher socket band, and ask Oracle about terms for your deployment. HeatWave pricing is not included in these server licence figures.

MySQL Community Edition is free under the GPL, and the product's Community pages describe open collaboration, transparent processes and community participation. That makes it a different proposition from a hosted-only database: teams can choose the Community Edition rather than buying an Enterprise server licence. The paid editions and OEM/embedded licensing have separate commercial terms, so confirm the licence that applies to your intended use with Oracle.

The product pages position HeatWave as a cloud service, but MySQL's other editions give teams database deployment options beyond that service. Treat migration as an application and data project: assess SQL compatibility, schema behavior, client dependencies and the destination database before planning an exit. Confirm your data export and migration options against the relevant MySQL documentation and contract. The sources do not establish a vendor-provided export guarantee or a particular lock-in mechanism.

Before production, choose the edition and check socket counts: paid Standard, Enterprise and Cluster prices differ by server tier, and Community Edition's socket and seat limits are not published. Enterprise Edition includes technical support and management tools; verify which features, service commitments and security controls match your requirements. The homepage describes scalability, security, reliability and uptime as Enterprise goals, but does not name compliance certifications or service-level targets. Ask Oracle for those details before relying on them.

Reddit discussions reflect mixed operational experience rather than a settled performance verdict. Some commenters point to replication, tooling and connection handling as practical benefits; others prefer PostgreSQL or MariaDB, and one commenter raises transaction-error concerns. A performance comparison in another thread drew questions about methodology, workload and topology. That is a useful reminder to validate your own query patterns, failure handling, backups and recovery process. For Cluster or HeatWave, confirm the deployment limits and operating responsibilities that apply to your configuration.