NOTE
1.14 MySQL Architecture
1. MySQL Logical Architecture Diagram 1. The client requests the server 2. The server's connection manager handles connections 3. The server's query optimizer handles SQL - After a query statement is parsed, it is handed to the query optimizer for optimization. The result of optimization is a so-called execution plan - This execution plan indicates which indexes should be used for the query and the join order between tables 4. Finally, according to the steps in the execution plan, methods provided by the storage engine are called to actually execute the query and return the query result to the user 2. MySQL Components
This is a historical learning note and may contain outdated or incomplete understanding.
1. MySQL Logical Architecture Diagram
- The client requests the server.
- The server’s connection manager handles connections.
- The server’s query optimizer handles SQL.
- After a query statement is parsed, it is handed to the query optimizer for optimization. The result of optimization is a so-called execution plan.
- This execution plan indicates which indexes should be used for the query and what the join order between tables should be.
- Finally, according to the steps in the execution plan, methods provided by the storage engine are called to actually execute the query and return the query result to the user.
2. MySQL Components
2.1. Server Layer
- Responsible for components related to MySQL functionality.


Discussion
Sign in with GitHub to comment. Discussions are stored as GitHub Issues.View on GitHub