Book Image

Hands-On Design Patterns with Kotlin

By : Alexey Soshin
Book Image

Hands-On Design Patterns with Kotlin

By: Alexey Soshin

Overview of this book

Design patterns enable you as a developer to speed up the development process by providing you with proven development paradigms. Reusing design patterns helps prevent complex issues that can cause major problems, improves your code base, promotes code reuse, and makes an architecture more robust. The mission of this book is to ease the adoption of design patterns in Kotlin and provide good practices for programmers. The book begins by showing you the practical aspects of smarter coding in Kotlin, explaining the basic Kotlin syntax and the impact of design patterns. From there, the book provides an in-depth explanation of the classical design patterns of creational, structural, and behavioral families, before heading into functional programming. It then takes you through reactive and concurrent patterns, teaching you about using streams, threads, and coroutines to write better code along the way By the end of the book, you will be able to efficiently address common problems faced while developing applications and be comfortable working on scalable and maintainable projects of any size.
Table of Contents (13 chapters)

Mutexes

Also known as mutual exclusions, mutexes provide a means to protect a shared state.

Let's start with same, old, dreaded counter example:

var counter = 0

val jobs = List(10) {
launch {
repeat(1000) {
counter++
yield()
}
}
}

runBlocking {
jobs.forEach {
it.join()
}
println(counter)
}

As you've probably guessed, this prints anything but the result of 10*100. Totally embarrassing.

To solve that, we introduce a mutex:

var counter = 0
val mutex = Mutex()

val jobs = List(10) {
launch {
repeat(1000) {
mutex.lock()
counter++
mutex.unlock()
yield()
}
}
}

Now our example always prints the correct number.

This is good for simple cases. But what if the code within the critical section (that is, between lock() and unlock()) throws an exception?

Then we'll...