Book Image

C++ Reactive Programming

By : Praseed Pai, Peter Abraham
Book Image

C++ Reactive Programming

By: Praseed Pai, Peter Abraham

Overview of this book

Reactive programming is an effective way to build highly responsive applications with an easy-to-maintain code base. This book covers the essential functional reactive concepts that will help you build highly concurrent, event-driven, and asynchronous applications in a simpler and less error-prone way. C++ Reactive Programming begins with a discussion on how event processing was undertaken by different programming systems earlier. After a brisk introduction to modern C++ (C++17), you’ll be taken through language-level concurrency and the lock-free programming model to set the stage for our foray into the Functional Programming model. Following this, you’ll be introduced to RxCpp and its programming model. You’ll be able to gain deep insights into the RxCpp library, which facilitates reactive programming. You’ll learn how to deal with reactive programming using Qt/C++ (for the desktop) and C++ microservices for the Web. By the end of the book, you will be well versed with advanced reactive programming concepts in modern C++ (C++17).
Table of Contents (20 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

The Cell pattern


We have already learned that reactive programming is all about processing values that vary over time. The reactive programming model is centered on the notion of Observables. There are two variants of Observables, which are as follows:

  • Cells: A cell is an entity (a variable, or a memory location) where values are regularly updated over time. They are also called properties or behaviors, in some contexts.
  • Streams: A stream represents a series of events. They are data that is often associated with actions. When people think of Observables, they have got stream variant of Observables in their mind.

We will implement a toy version of a Cell programming pattern. We will only focus on implementing basic functionality. The code needs tidying up for production use.

The following implementation can be optimized, if we are implementing a a controller class called Cell controller. . Then, the Cell controller class ( which contains a single Rx Subject for all cells)  can receive notifications...