This section is dedicated toward writing an R2DBC driver for database.

Service Provider Interface (SPI)

R2DBC defines an SPI all data store drivers must implement.

  • r2dbc-spi - set of interfaces defining the SPI for R2DBC.
  • r2dbc-spi-test - a Technology Compatibility Kit (TCK) contained within the SPI repository for verifying your driver’s implementation.

One noticeable difference between R2DBC and JDBC is that JDBC is aimed at both driver writers as well as application developers. Drivers and applications operate on different levels, making this one-size-fits-all less than ideal.

R2DBC’s SPI is deliberately designed to be as small as possible while still capturing critical features for ANY relational data store. This means that data store specific extensions are not targeted by the SPI.

And to ease implementation, a test interface, a veritable TCK, is provided to ensure you are fully operational.

Existing Drivers

R2DBC drivers implements the SPI listed above. The ones currently supported include:

  • r2dbc-postgres - driver implemented for PostgreSQL.
  • r2dbc-h2 - driver implemented for H2 as a test database.
  • r2dbc-mssql - driver implemented for Microsoft SQL Server.
  • cloud-spanner-r2dbc - experimental driver for Google Cloud Spanner
  • jasync-sql - Java & Kotlin Async DataBase Driver for MySQL and PostgreSQL written in Kotlin that has initial R2DBC support

Coding your own driver

R2DBC has a clearly defined SPI you must implement to host a solution for your data store. To build an implementation, add the following artifact to your build:

  • Group: io.r2dbc
  • Artifact: r2dbc-spi

The key interface all driver providers must implements is the Connection as shown below:

Publisher<Void> beginTransaction();
Publisher<Void> close();
Publisher<Void> commitTransaction();
Batch createBatch();
Publisher<Void> createSavepoint(String name);
Statement createStatement(String sql);
Publisher<Void> releaseSavepoint(String name);
Publisher<Void> rollbackTransaction();
Publisher<Void> rollbackTransactionToSavepoint(String name);
Publisher<Void> setTransactionIsolationLevel(IsolationLevel level);

Check out the specification for details on R2DBC Driver Compliance.

There are other parts to implement, but this is the core.

Technology Compatibility Kit (TCK)

R2DBC also has a suite of test cases to verify your support. Your data store implementation should import a test-scoped dependency on:

  • Group: io.r2dbc
  • Artifact: r2dbc-spi-test

To run all the tests that are expected, write an implementation of the TCK’s Example<T> test.

See r2dbc-postgresql’s Example to read the full source.