Book Image

Reactive Programming in Kotlin

By : Rivu Chakraborty
Book Image

Reactive Programming in Kotlin

By: Rivu Chakraborty

Overview of this book

In today's app-driven era, when programs are asynchronous, and responsiveness is so vital, reactive programming can help you write code that's more reliable, easier to scale, and better-performing. Reactive programming is revolutionary. With this practical book, Kotlin developers will first learn how to view problems in the reactive way, and then build programs that leverage the best features of this exciting new programming paradigm. You will begin with the general concepts of Reactive programming and then gradually move on to working with asynchronous data streams. You will dive into advanced techniques such as manipulating time in data-flow, customizing operators and provider and how to use the concurrency model to control asynchronicity of code and process event handlers effectively. You will then be introduced to functional reactive programming and will learn to apply FRP in practical use cases in Kotlin. This book will also take you one step forward by introducing you to Spring 5 and Spring Boot 2 using Kotlin. By the end of the book, you will be able to build real-world applications with reactive user interfaces as well as you'll learn to implement reactive programming paradigms in Android.
Table of Contents (20 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Dedication
Preface

Resource management


Resource management, what does it mean? Why should we care about it? If you've a little experience in application development with Java,Kotlin,JavaScript, or any other language, then you're probably familiar with the fact that while developing applications, we often need to access resources, and we must close them when we are done.

If you're not experienced with that phrase, resource management, then let's break things down. We will be starting from the ground by exploring the definition of a resource.

So, what is resource? When developing applications, you may often need to access an API (through an HTTP connection), access a database, read from/write to a file, or you may even need to access any I/O ports/sockets/devices. All these things are considered resources in general.

Why do we need to manage/close them? Whenever we are accessing a resource, especially to write, the system often locks it for us, and blocks its access to any other program. If you don't release or...