You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Part 4 - Concurrency/4. Backpressure.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ Here, the producer has its values ready and can emit them with no delay. The con
22
22
23
23
But this is only for synchronous execution. It is very common for the producer and the consumer to be asynchronous So, what happens when a producer and a consumer operate asynchronously at different speeds?
24
24
25
-
Let's first consider the traditional pull-based model, such as an iterator. In a pull-based model, the consumer requests the values. If the producer is slower, the consumer will block on request and resume when the next value arrives. If the procuder is faster, then it will have idle time waiting for the consumer request the next value.
25
+
Let's first consider the traditional pull-based model, such as an iterator. In a pull-based model, the consumer requests the values. If the producer is slower, the consumer will block on request and resume when the next value arrives. If the procuder is faster, then the producer will have idle time waiting for the consumer to request the next value.
26
26
27
27
Rx push-based, not pull-based. In Rx it is the producer that pushes values to the consumer when the values are ready. If the producer is slower, then the consumer will have idle time waiting for the next value to arrive. If producer is faster, without any provisions, it will keep force-feeding data to consumer without ever knowing about the consumer's difficulties.
0 commit comments