MySQL chooses the right storage engine

1 MyISAM: Default MySQL plug-in storage engine. If the application is based on read and insert operations,
There are very few updates and deletions, and the integrity and concurrency requirements for transactions are not very high, select this
The storage engine is very suitable. MyISAM is the most commonly used storage engine in the Web, data warehousing, and other application environments
One.
2 InnoDB: For transactional applications, foreign keys are supported. If the application has a higher integrity for the transaction
Requirements, data consistency is required under concurrent conditions, and data operations include many updates, in addition to inserts and queries,
Delete operation, the InnoDB storage engine should be the more appropriate option. In addition to effectively reducing the InnoDB storage engine
Because of the lock caused by the deletion and update, you can also ensure that the transaction is committed and rolled back (Rollback).
For systems like billing systems or financial systems that require high data accuracy, the InnoDB is the right choice
Choose.
3 MEMORY: Keep all your data in RAM, in environments where you need to quickly locate records and other similar data
Provides extremely fast access. MEMORY defect is the size of the table is limited, too large table cannot cache
Storage, the second is to ensure that the table data can be restored, the database after the termination of the data in the table can be recovered.
MEMORY tables are often used to update less frequent small tables for quick access to results.
4 MERGE: Used to logically group together a series of equivalent MyISAM tables and act as an object
Reference them. The advantage of the MERGE table is that it can break the limit on the size of a single MyISAM table, and by using different
Tables are distributed across multiple disks and can effectively improve the access efficiency of the merge table. This is for vldb such as data warehousing
Environment is very suitable.

5. In addition to MySQL's own storage engine, there are third-party storage engines, such as Columnstore engine infobright, high write performance compression tokudb, etc.

MySQL chooses the right storage engine