Book Image

Scala Reactive Programming

By : Rambabu Posa
Book Image

Scala Reactive Programming

By: Rambabu Posa

Overview of this book

Reactive programming is a scalable, fast way to build applications, and one that helps us write code that is concise, clear, and readable. It can be used for many purposes such as GUIs, robotics, music, and others, and is central to many concurrent systems. This book will be your guide to getting started with Reactive programming in Scala. You will begin with the fundamental concepts of Reactive programming and gradually move on to working with asynchronous data streams. You will then start building an application using Akka Actors and extend it using the Play framework. You will also learn about reactive stream specifications, event sourcing techniques, and different methods to integrate Akka Streams into the Play Framework. This book will also take you one step forward by showing you the advantages of the Lagom framework while working with reactive microservices. You will also learn to scale applications using multi-node clusters and test, secure, and deploy your microservices to the cloud. By the end of the book, you will have gained the knowledge to build robust and distributed systems with Scala and Akka.
Table of Contents (16 chapters)

Backpressure

In this section, we will discuss backpressure, one of the most important key concepts of Akka Streams supported features, with some simple and useful diagrams.

The main goal of the Akka Streams API is to support asynchronous streaming data with non-blocking backpressure, so as to support better performance and ease of maintainability for fast data-processing applications. It's therefore very important to understand what backpressure is, how it works, and why we need it in Akka Streams.

In Akka Streams, backpressure is a technique for flow-control between a Producer and a Consumer. It gives a way for the Consumer to inform the Producer about the number of data elements or messages it can accept so that the Producer sends only that number of data elements to the Consumer to avoid failures such as OutOfMemory issues.

Before moving to Akka-style backpressure, we...