-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
R2DBC support #15
Comments
@karim789 Hi, we can definitely look into this suggestion. Is there some specific project/use-case that you need this support in SODA for, or is it more of a general request? Thank you, |
We planned to use soda in the long term, but we had to improve performances first, and went for reactor, then realized that r2dbc was required if you want to have transactions. Now the time of using soda is coming but, it doesn't supports r2dbc. We will use oracle json_document directly for now and do manual queries with R2DBC API, until we can integrate soda more properly. |
Hi, thank you for the reply. SODA performance, and in particular SODA Java, is highly optimized. So you should be getting very high throughput and low latency with it, assuming statement caching is turned on on the JDBC connection, and SODA metadata caching is turned on. To turn on metadata caching:
There are some other gotchas we've seen other users encounter, that can degrade performance (it's a matter of using the API correctly). We'll evaluate whether we can add R2DBC support (note that R2DBC is pre-production right now), but also if you'd like to discuss whether the current SODA (just based on JDBC) is going to meet your desired performance needs (I would be very surprised if it did not), please feel free to email me at: maxim dot orgiyan at oracle dot com (remove space, replace "dot" with "." and "at" with "@") Thank you! |
Sorry, I meant we used Reactor to maximise our CPU usage, and this was not related to soda or a database, we have no performances issue with them. Then later when we added database support, and JDBC isn't working with @transactional and Reactor, so we had to use R2DBC. And now that we want to use soda, it's not compatible with R2DBC yet. Thanks for your answer. |
Hi,
The client only support JDBC connections, and now R2DBC would be great.
Regards
The text was updated successfully, but these errors were encountered: