Building Applications with Spring 5 and Kotlin

Solving the multithreading issue

There is no single solution for solving problems with the multithreading practices that we described previously. All solutions are dependent on the nature of the specific problem you have, as well as the existing architecture of your software.

For example, the solution to the problem of having your variables globally visible and modifiable can be prevented by using synchronization—but that can be costly in terms of performance. So, once again, think twice if you intend to expose something globally. There can be other ways to achieve the same goal.

If you have a tendency to create a lot of new threads running for the same functionalities, a better solution could be to have only one thread running and performing ...