Book Image

Hands-On Reactive Programming with Python

By : Romain Picard
Book Image

Hands-On Reactive Programming with Python

By: Romain Picard

Overview of this book

Reactive programming is central to many concurrent systems, but it’s famous for its steep learning curve, which makes most developers feel like they're hitting a wall. With this book, you will get to grips with reactive programming by steadily exploring various concepts This hands-on guide gets you started with Reactive Programming (RP) in Python. You will learn abouta the principles and benefits of using RP, which can be leveraged to build powerful concurrent applications. As you progress through the chapters, you will be introduced to the paradigm of Functional and Reactive Programming (FaRP), observables and observers, and concurrency and parallelism. The book will then take you through the implementation of an audio transcoding server and introduce you to a library that helps in the writing of FaRP code. You will understand how to use third-party services and dynamically reconfigure an application. By the end of the book, you will also have learned how to deploy and scale your applications with Docker and Traefik and explore the significant potential behind the reactive streams concept, and you'll have got to grips with a comprehensive set of best practices.
Table of Contents (16 chapters)

Communication patterns and observables

All the examples studied up to now were implemented as a single process. But software of a higher complexity, running either on the backend side or on the edge side, is usually split into multiple processes, and on multiple systems or devices. Communicating between processes and systems can be done in many different ways, and many solutions exist. For backend communication, one solution is to expose REST-oriented APIs, such as the audio transcoding service implemented throughout this book. The advantage of this solution is that it is easy to integrate with many existing tools. However, from a reactive point of view, it means that observables cannot be exposed outside the service: an HTTP request completes as soon as the first answer is sent, while an observable can send many items.

In cases where several services are implemented in a reactive...