MyISAM
the default database engine before Mysql5.5 is most commonly used. High insertion, query speed, but no transaction support
InnoDB
the preferred engine for transactional databases, supporting ACID transactions, support row-level locking , MySQL 5.5 as the default database engine
BDB from Berkeley db, another option for transactional databases that supports other transactional features such as COMMIT and ROLLBACK
Memory
all data is placed into the memory of the storage engine, with extremely high insertion, update and query efficiency. However, it occupies a memory space that is proportional to the amount of data. and its contents are lost when Mysql restarts
Merge
a certain number of MyISAM tables Unite as a whole and are useful for ultra-large data storage
Archive
ideal for storing large numbers of independent, historical data. Because they are not often read. Archive has an efficient insertion speed, but its support for queries is relatively poor
Federated
The different The Mysql server unites logically to form a complete database. Ideal for distributed Applications
Cluster/ndb
A highly redundant storage engine that provides services in conjunction with multiple data machines to improve overall performance and security. Suitable for applications with high data volumes, security and performance requirements
Csv
a storage engine that logically divides data by commas. It creates one for each data table in the database subdirectory . CSV file. This is an ordinary text file, where each row of data occupies a line of text. the CSV storage engine does not support indexing.
Blackhole
black hole engine, any data written will disappear, generally used to record binlog do replication relay
EXAMPLE
The storage engine is a stub engine that doesn't do anything. It is intended as An example of MySQL source code to demonstrate how to start writing a new storage engine. Similarly, its main interest is to developers. the EXAMPLE storage engine does not support indexing.
MySQL Storage engine record