oracle / oracle/nosql-java-sdk
Reactive Support
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 34
- Forks
- 27
- Avg merge
- 13h 59m
- Merged PRs (30d)
- 2
Description
Seems that you are using Netty for HttpClient implementation.
Although async is not supported yet, maybe it would be better to use Reactor Netty instead for reactive support?
Adding reactive support would improve already existing implementation for Spring Oracle NoSQL SDK (currently it just wraps synchronous requests, that doesn't open real reactive programming perspectives) and allow using NoSQL SDK in real reactive environments.
If it is welcome, I can realize such functionality as separate module and send a pull request. But please, add at least a marker interface for oracle.nosql.driver.http.Client so driver (like QueryDriver) can set other client implementations.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading oracle.nosql.driver.http.Client and QueryDriver to understand how the current HTTP client is selected and how synchronous requests are wrapped. Review the existing Netty-based implementation and evaluate the proposed Reactor Netty approach, including whether a separate module is appropriate. Done means reactive environments can use a genuine reactive client while existing synchronous behavior remains supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100