Those things about MySQL (5) Selection of the build table storage engine

When MySQL sees the table, it encounters the Select storage Engine: MyISAM and InnoDB. What kind of storage engine is good?

1, MyISAM: Table lock, support full-text index, read concurrency performance is good.

2, InnoDB: Row lock, support transaction, support foreign key, write concurrency performance is good.

In fact, most of the companies now, MySQL's rules are using INNODB as the default storage engine, in addition to support transactions and row lock is the more important two reasons, in fact, MyISAM in the actual application scenario is not very meaningful, and one important reason is that the official support is strong. Oracle acquired InnoDB Early and later acquired MySQL, which now focuses on the InnoDB engine.

In addition, MyISAM table locks can seriously affect read operations for a long time when concurrent write operations occur.

How does that InnoDB make up for reading concurrency and indexing problems?

The index should not be solved by MySQL itself now, should use third party's software, for example: Es,sphinx;

As for the performance of the reading table, it can be completely solved from the aspects of architecture and cache, and the technology solution is very mature.

So, to create a MySQL data sheet please do not hesitate to choose: InnoDB.

Those things about MySQL (5) Selection of the build table storage engine