MySQL 8.0 Supported Storage Engines Comment: Supports transactions, row-level locking, and foreign keys Transactions: YES XA: YES Savepoints: YES *************************** 3. row *************************** Engine: MRG_MYISAM Support: YES Comment: Collection of identical MyISAM tables Transactions: NO XA: NO Savepoints: NO *************************** 4. row *************************** Engine: BLACKHOLE Support: YES Comment: /dev/null storage engine (anything you write to it disappears) Transactions: NO XA: NO Savepoints: NO *************************** 5. row *************************** Engine: MyISAM Support: YES Comment: MyISAM storage engine Transactions: NO XA: NO Savepoints: NO ... This chapter covers use cases for special-purpose MySQL storage engines. It does not cover the default InnoDB  storage engine or the  NDB  storage engine which are covered in Chapter 15,  The InnoDB Storage Engine  and Chapter 23,  MySQL NDB Cluster 8.0 . For advanced users, it also contains a description of the pluggable storage engine architecture (see Section 16.11, “Overview of MySQL Storage Engine Architecture” ). For information about features offered in commercial MySQL Server binaries, see  MySQL Editions , on the MySQL website. The storage engines available might depend on which edition of MySQL you are using. For answers to commonly asked questions about MySQL storage engines, see Section A.2, “MySQL 8.0 FAQ: Storage Engines” . MySQL 8.0 Supported Storage Engines • InnoDB : The default storage engine in MySQL 8.0.  InnoDB  is a transaction-safe (ACID compliant) storage engine for MySQL that has commit, rollback, and crash-recovery capabilities to protect user data.  InnoDB  row-level locking (without escalation to coarser granularity locks) and Oracle-style consistent nonlocking reads increase multi-user concurrency and performance.  InnoDB  stores user data in clustered indexes to reduce I/O for common queries based on primary keys. To maintain data integrity,  InnoDB  also supports  FOREIGN KEY  referential-integrity constraints. For more information about  InnoDB , see Chapter 15,  The InnoDB Storage Engine . • MyISAM : These tables have a small footprint. Table-level locking limits the performance in read/write workloads, so it is often used in read-only or read-mostly workloads in Web and data warehousing configurations. • Memory : Stores all data in RAM, for fast access in environments that require quick lookups of non-critical data. This engine was formerly known as the  HEAP  engine. Its use cases are decreasing;  InnoDB  with its buffer pool memory area provides a general-purpose and durable way to keep most or all data in memory, and  NDBCLUSTER  provides fast key-value lookups for huge distributed data sets. • CSV : Its tables are really text files with comma-separated values. CSV tables let you import or dump data in CSV format, to exchange data with scripts and applications that read and write that same format. 3398