Mysql storage engine myisam, innodb, and memory
Memory will be introduced later
Innodb supports transactions, foreign keys, and row locks. mysql does not.
Innodb does not support fulltext index types
Innodb does not save the specific number of rows
Auto_increment of innodb does not support joint Indexing
When innodb deletes a table, a row is deleted.
--------------------------------------------------------------------------------
Database Operation Optimization for large websites
1. read/write splitting. The primary/secondary mode is used to distribute data pressure and improve query speed.
2. Split databases horizontally or vertically according to business characteristics. To improve database access efficiency, you can simply change a large database to a small database and a large table to a small table. Generally, a database with many or more N records in a table can significantly reduce the service capability of the database. For example, the number of records in a mysql DATA table reaches about, performance is almost intolerable.
Next bottleneck in the database
1. Transaction operations: data tables designed in transactions are locked during operation. In this case, the data accessing these tables may be delayed.
2. Data Update: any table in the database will also be locked during data update, resulting in latency.
Memcache will not see the above situation.