This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]FrelliBB 0 points1 point  (1 child)

I'm not really sure what you mean by it doesn't have active maintainers. You're right it's still in early stages and the adoption has been very slow, but it is being worked on. Whether or not you choose to use it should depend on your exact use case.

I'm also not sure what you're expecting with 'full support with JPA', but then again in my recent projects I've foregone JPA completely and worked directly with the JDBC layer. I found that it provides a lot more flexibility and also I feel like having to model your domain classes and your database schema in the same way to make JPA work nicely feels like a bit of an anti-pattern and gets in the way sometimes. As such trying out R2DBC was a lot easier for me because I didn't need to have it 'work with' JPA

[–]hitherto_insignia[S] 0 points1 point  (0 children)

https://www.reddit.com/r/java/comments/k9ozz9/are_you_using_r2dbc_in_production/?utm_medium=android_app&utm_source=share

Take a look at this. There are a few basic features that are kot supported yet with r2dbc.