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)

Summary

In this chapter, we learned about the main benefits of reactive systems. Such systems should be responsive, resilient, elastic, and driven by messaging.

We also discussed the Java 9 Reactive Streams API and its most popular implementation, which is Rx.

Now you should better understand the difference between cold and hot Observable. A cold Observable starts working only when someone subscribes to it. A hot Observable, on the other hand, always emits events, even if nobody is listening.

We also discussed the concept of backpressure, implemented with Flowable. It allows for a feedback mechanism between the producer and consumer.

In addition, you should be familiar with the notion of multicasting using subjects. It allows us to send the same message to multiple listeners.

Finally, we discussed some resilience mechanisms, such as buffering and throttling, that allow us to accumulate...