GitHub user ptrdom added a comment to the discussion: reduce or remove use of Scala Futures in favour of sticking to reactive streams
It seems like an obvious choice that should have been made in the initial design by Akka team, so before anyone starts refactoring `R2dbcExecutor` I suggest trying to investigate why the was a seemingly conscious choice to operate on `Future`. There might be pros/cons to both approaches, so it might make sense to provide both `Future` and e2e streaming based `R2dbcExecutor` implementations and allow users to choose, even moving `R2dbcExecutor` out of internal API and allowing any implementation to be plugged in by users. GitHub link: https://github.com/apache/pekko-persistence-r2dbc/discussions/265#discussioncomment-14914911 ---- 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]
