MySQL's storage engine

The storage engine, also known as the table type, refers to the way that MySQL uses different technology settings for various scenarios to store tables.

Common ones are: Myisam,innodb,bdb,memery,merge,archive,federated,cluster/ndb,csv,blackhole.

Introduction to the scene:

MYISAM: Has a high insertion and query speed, but does not support transactions,

Innodb:mysql5.5+ 's default database, the preferred engine for transactional databases, supports acid (atomicity, consistency, independence, persistence) transactions and supports row-level locking

BDB: Transactional database, support for other transactional features such as commit and rollback

Memery: All data placed in the memory of the storage engine, with very high insertion, update and query efficiency. However, it consumes storage space that is proportional to the amount of data. And its contents are lost when MySQL restarts.

Merge: Combine a certain number of myisam into a single whole, which is useful for ultra-large data storage

Archive: Ideal for storing large amounts of independent data as historical records, as they are not often read. Archive has the insertion speed of universities, but its support for queries is poor.

Federated: Combine different MySQL servers to logically 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: Logically, the storage engine that splits the data. He would create a. csv file for each database in the database subdirectory. This is a plain text file, where each row of data occupies a line of text and does not support indexing.

Blackhole: Black hole engine, any data written will disappear, generally used to record Binlog (binary log) to do replication relay.

MySQL's storage engine