This is a complicated problem. MySQL has done the complicated part by itself. I only know about shared read locks and exclusive write locks. Only reading is parallel, and the others are serial, that is, executed one by one. Non-simultaneity and sequential order are actually the allocation of lock granularity. Different storage engines are different, and the inside of the database helps us do this complicated thing. http://blog.csdn.net/xifeijian/article/details/20313977 This is the most detailed article I have found. I have read it several times. It will take some time to study it before it can be fully applied to actual application scenarios.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
This is a complicated problem. MySQL has done the complicated part by itself. I only know about shared read locks and exclusive write locks. Only reading is parallel, and the others are serial, that is, executed one by one. Non-simultaneity and sequential order are actually the allocation of lock granularity. Different storage engines are different, and the inside of the database helps us do this complicated thing. http://blog.csdn.net/xifeijian/article/details/20313977 This is the most detailed article I have found. I have read it several times. It will take some time to study it before it can be fully applied to actual application scenarios.
Haha, I will also post an article http://hedengcheng.com/?p=771