Did everything about RxJava / R2dbc end up dying? ...
# kotest-contributorse
Emil Kantis
07/06/2025, 10:27 PMDid everything about RxJava / R2dbc end up dying? Feels like no one talks about that stuff anymore. Did people give up on it in favor of fibers / virtual threads?
Wondering if it's worthwhile adding similar support for R2dbc containers as we have for JDBC, but it looks abandoned even in the testcontainers-java repo..
s
sam
07/07/2025, 5:00 AMfrom my viewpoint it never really caught up, the programming style is ugly. We have virtual threads and coroutines that allow us to write things in a typical view, so what's the point.
e
Emil Kantis
07/07/2025, 5:32 AMYeah I agree.. the mental/programming model was shit.. but for database interaction, there's no streaming support outside of R2dbc, so wouldn't people still want to use it w/ coroutines?
s
sam
07/07/2025, 5:33 AMI just wrap spring jdbc in runInteruptible
sam
07/07/2025, 5:33 AMand we do 10m requests a minute
e
Emil Kantis
07/07/2025, 5:38 AMlol, I didn't know
runInteruptibleEmil Kantis
07/07/2025, 5:46 AMWe're not using r2dbc either.. but we had issues with blocking calls being run in
runBlockings
sam
07/07/2025, 8:40 AMjdbc doesn't actually respond to interruption properly
sam
07/07/2025, 8:40 AMyou can set a timeout though on the statement level that will interrupt the thread
s
Scott Fedorov
07/07/2025, 1:46 PMI totally agree with Sam about the R2DBC. I learned the spring library and man that’s some ugly code that really is just not very kotlin native. Was so clunky and the APIs just so different for such little benefit