testcontainers / testcontainers/testcontainers-java
Allow consumption of a relational database testcontainer through R2DBC
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
R2DBC is an initiative to establish a reactive API for relational database integration. It would be great to additionally consume a test container with a relational database through R2DBC by exposing the connection through a preconfigured ConnectionFactory.
ConnectionFactory is in R2DBC what a DataSource is in JDBC. R2DBC drivers are available for:
More to come eventually.
Right now I can think of the following consumption scenarios:
- Pure JDBC (available today)
- JDBC and R2DBC (would make a lot of sense for testing as JDBC can help to prevent additional synchronization in cases where fixtures are prepared via JDBC and the actual application consumes data using reactive APIs)
- R2DBC-only (useful in pure reactive environments)
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 tracing how relational database test containers currently expose JDBC access, then compare the R2DBC SPI ConnectionFactory entry point linked in the issue. Done means a relational database test container can be consumed through a preconfigured ConnectionFactory while existing JDBC and combined JDBC/R2DBC scenarios remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100