How to systematically understand and learn multi-threading and asynchronous models?

I have been doing php-web development before, and I have never been exposed to multi-threading and asynchronous models. Recently I need to use swoole to develop a websocket server. I saw that the document involves a lot of concepts about multi-threading and asynchronous models. How can I learn this knowledge systematically now?

Reply content:

I have been doing php-web development before, and I have never been exposed to multi-threading and asynchronous models. Recently I need to use swoole to develop a websocket server. I saw that the document involves a lot of concepts about multi-threading and asynchronous models. How can I learn this knowledge systematically now?

Personally, I don’t think there is anything that requires systematic learning, just go to the corner and face the wall to reflect.
Many students will encounter similar problems. The fundamental reason is that your thinking patterns are synchronized, and changing your thinking patterns cannot be solved by external forces. Asynchronous thinking is closer to reality. All behaviors in reality can be explained in an asynchronous way. That is, although I don’t know what will happen in the future, the measures I will take for specific things are certain (such as going to the toilet). In other words, the asynchronous model It is reasoning from beginning to end; in contrast, the synchronous model often deduces its rules in reverse based on the predicted conditions and prescribed results.
Multi-threading is relatively simple, as long as you have the awareness of thread management.

Additional explanation: The way of thinking has nothing to do with whether the final code is synchronous or asynchronous. However, if the way of thinking is wrong, it will be difficult to understand the ideas represented by the code of the asynchronous model, thus forming a learning obstacle.