The story that started 20 years ago is coming to its end. I’m talking about the old MyISAM storage engine that was the only storage provided by MySQL in 1995, and was available in MySQL for 20+ years. Actually, part of my job as a MySQL consultant for 10+ years was to discover MyISAM tables and advise customers how to convert those to InnoDB.

(Check your MySQL installation, you may still have MyISAM tables).

MySQL 5.7 still used MyISAM storage for the system tables in the MySQL schema.

In MySQL 8.0 (DMR version as of writing), the MyISAM storage engine is still available. But in a very limited scope:

• After introducing the new data dictionary, the MyISAM tables are gone from the system schema (“mysql” db).
• Working with MyISAM is harder now (and discouraged): You can’t just copy MyISAM tables into a running MySQL server. They will not be discovered (unlike InnoDB, where you can use “ALTER TABLE … IMPORT TABLESPACE”)
• However, you can create a table engine=MyISAM, and it will work as before

InnoDB implemented all the older, missing features:

So the only MyISAM advantages left are:

1. Tables will be smaller on disk compared to uncompressed InnoDB tables.
2. The count(*) is still much faster in MyISAM:

mysql> select count(*) from a_myisam;
+----------+
| count(*) |
+----------+
|  6291456 |
+----------+
1 row in set (0.00 sec)
mysql> select count(*) from a_innodb;
+----------+
| count(*) |
+----------+
|  6291456 |
+----------+
1 row in set (2.16 sec)

I would not use MyISAM unless there is a specific case, and for well-known reasons (MyISAM are non-transactional, table level locks, with no crash recovery, etc.)

My colleague Laurynas Biveinis also suggested converting MyISAM to an optional storage engine plugin.