MySQL
The relational server that ran the early web, now Oracle-stewarded and InnoDB-based.
Overall in database engines
3of 5 · score 63.5
Data coverage
100%
26 of 26 fields sourced
Best for
- •Very large tables that must be altered without downtime
- •Read-replica topologies your team has already run before
- •Environments where the host, ORM or ops runbook already assumes MySQL
Strong on
- +Online schema change Yes 1/5
- +Embedded or server Server (client/server) 1/5
- +Isolation levels Read uncommitted, Read committed, Repeatable read, Serializable 1/5
- +Managed options Amazon RDS, Amazon Aurora, Google Cloud SQL, Azure Database, PlanetScale 2/5
- +Migration tooling 4 2/5
- +JSON support Binary JSON type 2/5
Weak on
- −Extension ecosystem 2 5/5Better: PostgreSQL: 5
- −Embed in closed source No 5/5Better: SQLite: Yes
- −Ops burden 3 3/5Better: SQLite: 1
- −Vector search Native type 5/5Better: MariaDB: Native type + ANN index
vs MariaDB
- •Ahead on Client libraries: 5 vs 4
- •Ahead on Migration tooling: 4 vs 3
- •Behind on Vector search: Native type vs Native type + ANN index
- •Behind on Embed in closed source: No vs Partial
How MySQL scores among 5 database engines26 of 26 fields known
Engine & SQL10
Concurrency model2nd
MVCC (undo log)
2/5
Leader: PostgreSQL · MVCC (heap row versions)
dev.mysql.com · 2026-07-01
Isolation levels1st
Read uncommitted, Read committed, Repeatable read, Serializable
1/5
dev.mysql.com · 2026-11-06
JSON support2nd
Binary JSON type
2/5
Leader: PostgreSQL · Binary JSONB + indexes
dev.mysql.com · 2026-07-01
Operations7
Connection model3rd
Thread per connection
3/5
Leader: SQLite · In-process (no connections)
dev.mysql.com · 2026-07-01
Managed options2nd
Amazon RDS, Amazon Aurora, Google Cloud SQL, Azure Database, PlanetScale
2/5
Leader: PostgreSQL · Neon, Supabase, Amazon RDS, Amazon Aurora, Google Cloud SQL, Azure Database, PlanetScale
· 2026-07-01
Ops burden3rd
3
3/5
Leader: SQLite · 1
· 2026-07-01
Ecosystem5
Extension ecosystem
2
5/5
Leader: PostgreSQL · 5
· 2026-07-01
Client libraries1st
5
1/5
· 2026-07-01
Migration tooling2nd
4
2/5
Leader: PostgreSQL · 5
· 2026-07-01
Licence & governance3
History1
Alternatives4
Compare
Sources20
- www.mysql.com/about/legal/licensing/oem/2 fields
- dev.mysql.com/doc/refman/8.4/en/what-is-mysql.html1 field
- dev.mysql.com/doc/refman/8.4/en/innodb-multi-versioning.html1 field
- dev.mysql.com/doc/refman/8.4/en/innodb-locking.html1 field
- dev.mysql.com/doc/refman/8.4/en/innodb-transaction-isolation-levels.html1 field
- dev.mysql.com/doc/refman/8.4/en/json.html1 field
- dev.mysql.com/doc/refman/8.4/en/fulltext-search.html1 field
- dev.mysql.com/doc/refman/9.0/en/vector.html1 field
- dev.mysql.com/doc/refman/8.4/en/sql-mode.html1 field
- dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl-operations.html1 field
- dev.mysql.com/doc/refman/8.4/en/innodb-limits.html1 field
- dev.mysql.com/doc/refman/8.4/en/replication.html1 field
- dev.mysql.com/doc/refman/8.4/en/point-in-time-recovery.html1 field
- dev.mysql.com/doc/refman/8.4/en/innodb-online-ddl.html1 field
- dev.mysql.com/doc/refman/8.4/en/connection-interfaces.html1 field
- dev.mysql.com/doc/refman/8.4/en/server-system-variables.html1 field
- github.com/mysql/mysql-server1 field
- www.mysql.com/1 field
- www.mysql.com/about/1 field
- dev.mysql.com/doc/refman/8.4/en/history.html1 field