Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • C++ Reactive Programming
  • Toc
  • feedback
C++ Reactive Programming

C++ Reactive Programming

By : Praseed Pai, Abraham
3 (8)
close
C++ Reactive Programming

C++ Reactive Programming

3 (8)
By: Praseed Pai, 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 (15 chapters)
close

The limitations of the GoF Observer pattern


The GoF pattern book was written at a time when the world was really doing sequential programming. The architecture of Observer pattern implementation had lot of anomalies, judging from the current programming model world view. Here are some of them:

  • The close coupling between Subjects and Observers.
  • The lifetime of the EventSource is controlled by the Observers.
  • Observers (sinks) can block the EventSource.
  • The implementation is not thread-safe.
  • Event filtering is done at the sink level. Ideally speaking, the data should be filtered at the place where the data is (at the subject level, before notification).
  • Most of the time, Observers do not do much and the CPU cycles will be wasted.
  • The EventSource should ideally publish the value to the environment. The environment should notify all the subscribers. This level of indirection can facilitate techniques such as event aggregation, event transformation, event filtering, and canonicalizing the event data...
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete