Database server layer for common MySQL

The MySQL plug-in storage engine is a component in the MySQL database server that performs actual data I/O operations for the database and allows and enforces a specific set of attributes for special application requirements. One of the main advantages of using a special storage engine is that it requires only the features required for a particular application, so the system overhead in the database is small and the end result has more efficient and higher database performance. This is one of the reasons MySQL is always considered high-performance, and it can match or defeat proprietary monolithic databases in the industry standard benchmark.

From a technical standpoint, what are some of the unique components that support the underlying structure in the storage engine? Some key differences include:

· Concurrency: Some applications have a lot of granular locking requirements (such as row-level locking) than other applications. Choosing the right locking strategy can reduce overhead and help improve overall performance. It also includes support for multiple capabilities, such as multiple versions of concurrency control or "snapshot" reads.

· Transactional support: Not all applications require transactions, but there are well-defined requirements, such as acid compatibility, for applications that do need transactions.

· Referential integrity: The server needs to enforce referential integrity for the associated database by DDDL the defined foreign key.

· Physical storage: It includes a variety of items, from the total page size of the table and index, to the format needed to store the data, to the physical disk.

· Index support: Different applications tend to adopt different indexing strategies, and each storage engine usually has its own indexing method, but some index methods, such as the B-tree index, are common to almost all storage engines.

· Memory Cache: Different applications respond better to some memory caching strategies than other applications, so while some memory buffers are common to all storage engines (such as high-speed buffering for user connections, MySQL's high-speed query buffer, etc.), Other caching policies are uniquely defined only when using a special storage engine.

· Performance help: Includes multiple I/O threads for parallel operations, thread concurrency, database checkpoints, batch insert processing, and more.

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

Each set of plug-in storage engine basic components are designed to provide a selectable set of attributes for a particular application. From a negative point of view, avoiding the use of component attribute collections helps avoid unnecessary overhead. Therefore, it is obvious that you should understand the requirements set for a particular application and choose the appropriate MySQL storage engine that can significantly improve the overall efficiency and performance of the system.