Join GitHub today
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
More to come eventually.
Right now I can think of the following consumption scenarios:
I took a look at how R2DBC could be implemented and found that a suitable implementation might be hard to achieve because of the way how containers are organized.
Here are my thoughts:
SQL databases are assumed to be JDBC containers and not Database containers. Adding a
Ideally, database containers are represented as subclass of
This brings us ultimately to
If a test wants to use JDBC and R2DBC using URL-based container bootstrapping, then potentially, we would end up with two container instances. But what we rather want to achieve is a test setup where both integration technologies (JDBC and R2DBC) point to the same database (
That being said, a potential design could be:
This way, containers can be consumed without pulling R2DBC API and are appropriately segregated by access technology.
Let me know what you think, whether that is something worth pursuing.