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)
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.ConnectionFactoryis in R2DBC what aDataSourceis in JDBC. R2DBC drivers are available for:More to come eventually.
Right now I can think of the following consumption scenarios: