Common MySQL database server layer _ MySQL

The MySQL plug-in storage engine is a component in the MySQL database server. it performs actual data I/O operations for the database, and allows and enforces specific feature sets for special application requirements. One of the main advantages of using a special storage engine is that it only needs to provide the features required by special applications. Therefore, the system overhead in the database is small, and the final result has more effective and higher database performance. This is also one of the reasons why MySQL is always regarded as having high performance. in terms of industry standard benchmarks, it can rival or defeat proprietary monolithic databases.

Technically, what are some unique components that support the underlying structure of the storage engine? Key differences include:

· Concurrency: Some applications have a lot of granular locking requirements (such as row-level locking) than other applications ). Selecting the correct locking policy can reduce the overhead and improve the overall performance. It also supports multiple capabilities, such as multi-Version Concurrency control or "snapshot" reading.

· Transaction support: not all applications require transactions, but they have well-defined requirements for applications that do need transactions, such as ACID compatibility.

· Integrity of reference: the server must maintain the integrity of the reference of the associated database through the foreign key defined by DDDL.

· Physical storage: it includes various items, from the total page size of tables and indexes to the format required to store data, to the physical disk.

· Indexing support: different applications tend to adopt different indexing policies. each storage engine usually has its own indexing method, but some indexing methods (such as B-tree indexes) it is common for almost all storage engines.

· Memory high-speed buffer: compared with other applications, different applications provide better responses to some memory high-speed buffer policies. therefore, although some memory high-speed buffering is common to all storage engines (such as high-speed buffering for user connection and high-speed Query caching for MySQL ), other high-speed buffer policies are only defined when special storage engines are used.

· Performance help: it includes multiple I/O threads for parallel operations, Thread concurrency, database checkpoints, and batch insert processing.

· Other target features: may include support for geospatial operations and security restrictions on specific data processing operations.

The basic components of each plug-in storage engine are designed to provide a set of optional features for specific applications. From the opposite perspective, avoiding the use of component feature sets helps avoid unnecessary overhead. Therefore, it is obvious that you should understand the set of requirements for specific applications and select a MySQL storage engine that can greatly improve the overall efficiency and performance of the system.