In system handling for Reactive Programming, we have Publisher, which is the source of data, and Subscriber, which processes the emitted data. In normal situations, the data emitted by the Publisher is handled elegantly. However, the situation is not so simple every time. The rate at which the data is emitted by the Publisher is more than the rate at which the subscriber is consuming. It leads to overflowing data, putting pressure on the Subscriber. Backpressure is built whenever the Publisher is faster than the Subscriber. We already have discussed backpressure in detail in Chapter 1, Introduction to Reactive Programming.
Flow API doesn't provide any APIs that facilitate creating a mechanism to handle backpressure. As discussed earlier, sending a signal from the Subscriber to the Publisher will slow down the emission at the publisher end. Though...