Skip to content
This repository has been archived by the owner on Jun 24, 2020. It is now read-only.

Future of R2DBC Client #63

Closed
mp911de opened this issue Oct 17, 2019 · 0 comments
Closed

Future of R2DBC Client #63

mp911de opened this issue Oct 17, 2019 · 0 comments
Labels
for: team-attention An issue we need to discuss as a team to make progress

Comments

@mp911de
Copy link
Member

mp911de commented Oct 17, 2019

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.

@mp911de mp911de added the for: team-attention An issue we need to discuss as a team to make progress label Oct 17, 2019
pacphi added a commit to cf-toolsuite/cf-butler that referenced this issue Dec 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
for: team-attention An issue we need to discuss as a team to make progress
Projects
None yet
Development

No branches or pull requests

1 participant