COROUTINE

Kotlin recommends using Corutines for asynchronous programming. There are quite a few architectural nuances that determine the use of a coprogram. In most cases, asynchronous tasks are simply run in separate threads. This is a simpler standard solution, the effectiveness of which depends on the complexity of your project. However, if each thread and switching between them requires a significant amount of resources, you need to reduce the number of threads and the load on the system, or use only one thread at all, as in JavaScript, it is more profitable to use coprograms. They are also appropriate, for example, if the project has a lot of mutable states with which a function can return different values with the same arguments. Or if you can change the UI only from its thread, and so on.

The use of Coroutines significantly improves program performance. Suspending functions without blocking a thread can significantly save resources. In a standard situation, when only a few of the total number of threads are active, blocking one of them slows down a specific process and the entire work in general. Suspending a coprogram, in turn, does not require the cost of switching threads and using OS mechanisms.

In the user library, you can fine-tune the conditions for the operation of the coprogram. Developers can not only simply add suspension conditions, but also optimize them, log them, and much more. At the same time, coprograms require strict binding to breakpoints - each needs at least one suspend function that explains where you can safely stop calculations so that they can be easily resumed during the next call.

Kotlin makes it easy to use Corutines in projects thanks to support in many Jetpack libraries. Some of them have their own co-programming areas, which make it easy to create structured parallelism and, among other benefits, also reduce memory leaks.