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
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We know that data is pushed from the
read-side
to thewrite-side
using gRPC. Both theread-side
andwrite-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 thewrite-side
does? This situation can result in thewrite-side
falling behind in consuming the data.This is a classic producer-consumer problem.
Beta Was this translation helpful? Give feedback.
All reactions