Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Reactive Programming in Kotlin

You're reading from   Reactive Programming in Kotlin Design and build non-blocking, asynchronous Kotlin applications with RXKotlin, Reactor-Kotlin, Android, and Spring

Arrow left icon
Product type Paperback
Published in Dec 2017
Publisher Packt
ISBN-13 9781788473026
Length 322 pages
Edition 1st Edition
Languages
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Rivu Chakraborty Rivu Chakraborty
Author Profile Icon Rivu Chakraborty
Rivu Chakraborty
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. A Short Introduction to Reactive Programming 2. Functional Programming with Kotlin and RxKotlin FREE CHAPTER 3. Observables, Observers, and Subjects 4. Introduction to Backpressure and Flowables 5. Asynchronous Data Operators and Transformations 6. More on Operators and Error Handling 7. Concurrency and Parallel Processing in RxKotlin with Schedulers 8. Testing RxKotlin Applications 9. Resource Management and Extending RxKotlin 10. Introduction to Web Programming with Spring for Kotlin Developers 11. REST APIs with Spring JPA and Hibernate 12. Reactive Kotlin and Android

Flowable and Subscriber


Instead of Observer, Flowable uses Subscriber, which is backpressure compatible. However, if you use lambda expressions, then you will not notice any differences. So, why use Subscriber instead of Observer? Because Subscriber supports some extra operations and backpressure. For instance, it can convey how many items it wishes to receive as a message to upstream. Or rather, we can say while using Subscriber; you must specify how many items you want to receive (request) from upstream; if you don't specify it, you will not receive any emissions.

As we already mentioned, using lambda with Subscriber is similar to Observe; this implementation will automatically request an unbounded number of emissions from the upstream. As with our last code, we didn't specify how many emissions we want, but it internally requested unbounded number of emissions, and that's why we received all the items emitted.

So, let's try replacing the previous program with a Subscriber instance:

    fun...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at R$50/month. Cancel anytime