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

Memory ordering


We have already learned about the atomic types and atomic operators available in the standard library. While performing operations on atomic types, we need to specify memory ordering for certain operations. Now, we will talk about the significance and use cases for the different memory-ordering semantics. The key idea behind atomic operations is to provide synchronization in data access across multiple threads, and this is achieved by enforcing the order of execution. For example, if writing to the data happens before the read from the data, things will be fine. Otherwise, you are in trouble! There are six memory-ordering options available with the standard library that can be applied to operations on atomic types: memory_order_relaxed, memory_order_consume, memory_order_acquire, memory_order_release, memory_order_acq_rel, and memory_order_seq_cst. For all atomic operations on atomic types, memory_order_seq_cst is the memory order by default unless you specify something else...