list the trade-offs of programming with such frameworks as reactivex kotlin-coroutines akka-actors?

Threads, coroutines, actors, etc are all abstractions around concurrent operations. The main tradeoffs here are the number of those concurrent operations and the duration for which they are active.

OS-level threads work really well when you have a few concurrent operations (since each thread expensive) and when all operations do big chunks of CPU-bound work (since switching between threads is very expensive).

User-level abstractions of all sorts that are created on top of OS-level threads work well when you have lots of those concurrent operations and/or they consume very little CPU from their start to finish or from one resumption point to the next suspension, since those abstractions are light-weight and their launching, stopping, and switching between them is very cheap, too.

CLICK HERE to find out more related problems solutions.

Leave a Comment

Your email address will not be published.

Scroll to Top