Scala Reactive Programming

Pull – Slow Producer/Fast Consumer

Let's consider another scenario in this section. For instance, a pull-based backpressure application has a Slow Producer/Fast Consumer scenario.

In this case, Consumer should always try to pull more messages from Producer, and Producer is a bit slow in sending messages to Consumer. So, Consumer should wait to receive new messages. This is also not a good approach.

So finally, neither the pull-based approach nor the push-based approach is an ideal solution for solving streaming data problems. We should find a new approach that combines both of these two approaches. This new approach should work dynamically, meaning that it should pick up one of these approaches depending on the context and try to solve the ...