Book Image

Learning Concurrency in Kotlin

By : Miguel Angel Castiblanco Torres
Book Image

Learning Concurrency in Kotlin

By: Miguel Angel Castiblanco Torres

Overview of this book

Kotlin is a modern and statically typed programming language with support for concurrency. Complete with detailed explanations of essential concepts, practical examples and self-assessment questions, Learning Concurrency in Kotlin addresses the unique challenges in design and implementation of concurrent code. This practical guide will help you to build distributed and scalable applications using Kotlin. Beginning with an introduction to Kotlin's coroutines, you’ll learn how to write concurrent code and understand the fundamental concepts needed to write multithreaded software in Kotlin. You'll explore how to communicate between and synchronize your threads and coroutines to write collaborative asynchronous applications. You'll also learn how to handle errors and exceptions, as well as how to work with a multicore processor to run several programs in parallel. In addition to this, you’ll delve into how coroutines work with each other. Finally, you’ll be able to build an Android application such as an RSS reader by putting your knowledge into practice. By the end of this book, you’ll have learned techniques and skills to write optimized code and multithread applications.
Table of Contents (11 chapters)


This chapter has introduced many new topics that are going to be needed for the upcoming, more advanced topics. Let's review the chapter once more to refresh our memory:

  • We started by doing some Android programming, creating a RecyclerView and displaying the news from the RSS feeds.
  • We talked about how an Adapter maps a set of data into views, and how a ViewHolder is used as part of that.
  • We learned that Android's RecyclerView will avoid creating views as much as possible; instead, it will recycle them as the user scrolls.
  • We talked about suspending functions, and learned that they offer a flexible way to define suspending code.
  • We mentioned that async functions – a function returning an implementation of Job – should never be part of a public API, to avoid the risk of forcing a certain implementation.
  • We covered the interesting topic of the coroutine...