MySQL Storage engine
MySQL database has many kinds of storage engine, different engine features different, have their own advantages. I've been looking at the MySQL Technology insider, just taking notes.
InnoDB Storage Engine
This is the default storage engine since MySQL 5.5.8, and is also my usual search engine. Supports transactional operations, primarily for online transaction processing applications, characterized by row lock design, support for foreign keys, and support for non-locked read-like reads such as Oracle does not generate locks.
By using versioning to get high concurrency and implementing the four isolation levels of the SQL standard, the default is the repeatable level (which prevents dirty reads and non-repeatable reads). Also use a Next-key locking strategy to write two times the Adaptive Hash Index, pre-read and other high performance and highly available functions.
InnoDB is a cluster engine.
MyISAM Storage Engine
This engine does not support transactions and does not support table lock design, but it supports full-text indexing.
This is the default storage engine (except Windows) before MySQL 5.5.8.
NDB Storage Engine
I have not used this engine, but this engine seems to be more powerful.
It is a clustered storage engine, similar to a RAC cluster, and is an OLTP-oriented database application.
Memory Storage Engine
The engine is to put all the data in memory, so, restart or crash, all the data will be lost. So it is more suitable for temporary table such application scenario, Data Warehouse dimension table these applications. The default is a hash index, not a B + tree.
Infobright Storage Engine
This is a third-party storage engine whose storage is stored in columns. Not a row store. Therefore, it is suitable for OLAP data application.
Ntse Storage Engine
NetEase developed the engine, as its own internal use, does not support transaction management (as if to support later).
There are many other engines.
Note: 2015/04/13
MySQL learning-MySQL storage engine notes