GitHub user mdedetrich added a comment to the discussion: Artifical back 
pressure on JDBC projections

> How would backpressure work in this case? Would all the other streams start 
> signaling to this stream that works so well that they are not receiving any 
> elements and that this well working stream should slow down? 

Yes, if you use the pekko-streams API this is exactly what fan-in/fan-out API's 
do.

My point is that current implementation is not even a stream at all, look at 
the API at 
https://github.com/apache/pekko-persistence-r2dbc/blob/beee0d1bfd0cd46969e8ab940cf8244e7f07b5b3/projection/src/main/scala/org/apache/pekko/projection/r2dbc/internal/R2dbcOffsetStore.scala,
 as you can see its all `Future` based which means that we essentially lose all 
of the dynamic backpressuring goodness that pekko/reactive streams/r2dbc gives 
us



GitHub link: 
https://github.com/apache/pekko/discussions/2431#discussioncomment-14894269

----
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]

Reply via email to