A little sentiment about golang concurrent programming

This is a created article in which the information may have evolved or changed.

• The core of concurrent programming is the use of time planning .
• Concurrent programming gives programmers more freedom to abstract design models from the real world

If each person in the team is considered to be 1, then the communication between them is the channel, and the collaborative process is the business logic

Their own application scenarios for concurrent programming Some summary (say the wrong place, everyone do not want to shoot bricks):

1. The simultaneous execution of different operations can be done asynchronously using a co-process
2. All the relatively independent high repetition business, can adopt the multi-coprocessor concurrent processing
3. Where can be disassembled into a number of relatively independent small-step business, each step can also be multi-coprocessor concurrent processing
4. When decoupling or inversion of control is required between modules, consider using the inter-channel communication to solve

Finally, it is important to note that the critical resources in the concurrency environment read and write security, the use of static variables and read-write lock!