GitHub user mdedetrich added a comment to the discussion: Artifical back pressure on JDBC projections
But that is the whole point of r2dbc/backpressure, as long as the entire flow is a stream then r2dbc will automatically slow itself down so it won't overwhelm the database. Right now even if you use postgres-r2dbc projection adaptor it won't do this because we just use the future API, which means it will send out transactions/statements as fast as the connection can handle. Of course I can't say for certain if it will help this scenario as I am not aware of the details, but the whole point of bi-directional backpressure (which is what pekko-streams and r2dbc implement) is to avoid manually throttling as both the consumers and products for each stream in the pipeline signal how fast they can produce and/or how fast they can consume GitHub link: https://github.com/apache/pekko/discussions/2431#discussioncomment-14894146 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
