Overview (Reactive Relational Database Connectivity

Packages
Package	Description
io.r2dbc.spi	The Service Provider Interface for R2DBC.

R2DBC is a specification designed for reactive programming with SQL databases.

R2DBC stands for Reactive Relational Database Connectivity. Reactive in the sense of an event-driven, non-blocking, and functional programming model that does not make assumptions over concurrency or asynchronicity. Instead, it assumes that scheduling and parallelization happen as part of runtime scheduling.

R2DBC specifies a service-provider interface (SPI) that is intended to be implemented by driver vendors and used by client libraries. By using the R2DBC SPI, applications written in a JVM programming language can run SQL statements and retrieve results by using an underlying data source. You can also use the R2DBC SPI to interact with multiple data sources in a distributed, heterogeneous environment. R2DBC targets primarily, but is not limited to, relational databases. It aims for a range of data sources whose query and statement interface is based on SQL (or an SQL-like dialect) and that represent their data in a tabular form.

Driver Entry Points

A driver should implement the following interfaces as entry-points:

ConnectionFactoryProvider: Discovery and configuration component.
ConnectionFactory: Entry-point to create a Connection.

Consumer Entry Points

A R2DBC consumer interacts primarily with the following interfaces:

ConnectionFactories: Obtain a ConnectionFactory using a R2DBC Connection URL or programmatic configuration.
ConnectionFactory: Entry-point to create a Connection.

Reactive Relational Database Connectivity - SPI 0.9.1.RELEASE API

Driver Entry Points

Consumer Entry Points