We know that data is pushed from the read-side to the write-side using gRPC. Both the read-side and write-side consult a throttler and limit their own consumption based on its recommendations.
But what if the read-side determines that it doesn't need to limit consumption, while the write-side does? This situation can result in the write-side falling behind in consuming the data.
This is a classic producer-consumer problem.