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)

Pipelines

In our StoryLand, the same lazy architect, me, is struggling with a problem. Back in Chapter 4, Getting Familiar with Behavioral Patterns, we wrote an HTML page parser. But it depends on whether somebody already fetched the pages to parse for us. It is also not very flexible.

What we would like is for one coroutine to produce an infinite stream of news, and for others to parse that stream in steps.

To start working with DOM, we'll need a library, such as kotlinx.dom. If you're using Gradle, make sure you add the following lines to your build.gradle:

repositories {
...
jcenter()
}

dependencies {
...
compile "org.jetbrains.kotlinx:kotlinx.dom:0.0.10"
}

Now, to the task at hand.

First, we would like to fetch news pages once in a while. For that, we'll have a producer:

fun producePages() = produce {
fun getPages(): List<String&gt...