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)

What to do when nothing happens

One of the most common issues when starting developing with ReactiveX is the issue that "nothing happens". There are several ways to avoid this, mostly by following the same development principles as any other piece of code:

  • Write small parts of code and test them with unit tests. Whenever possible, follow test-driven development (TDD). It feels like a waste of time in the beginning, but from my experience it saves time as soon as the first development release is delivered.
  • Develop the application step-by-step, with something that executes as early as possible. The initial implementation will be full of stubs, but they are already doing something. With each feature being implemented one after an other, finding an issue is easier.

Following these simple principles, you may still not make any progress. In this case, using the do_action...