This repository has been archived by the owner on Jun 24, 2020. It is now read-only.
Future of R2DBC Client #63
Labels
for: team-attention
An issue we need to discuss as a team to make progress
R2DBC started as an experiment to evaluate whether reactive programming and SQL databases can work together. R2DBC Client emerged as an artifact to make R2DBC usable without the need to use the SPI directly. A library that is providing higher-level abstraction, which is taking care of resource handling and a more humane API.
With the growth of drivers and the adoption of R2DBC in the Java eco-system, R2DBC Client deserves a place where it can evolve and reside in a maintained state. R2DBC is not opinionated about clients and client design in particular. Maintaining R2DBC Client by the R2DBC team and within the R2DBC organization influences how client library development is perceived.
R2DBC has a neutral position regarding client library design.
Therefore we want to transition R2DBC client into a new home that allows for the development and evolution of the client inspired by JDBI.
The text was updated successfully, but these errors were encountered: