db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Paluch (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-7036) Investigate an R2DBC client implementation
Date Sat, 23 Feb 2019 20:46:00 GMT
Mark Paluch created DERBY-7036:
----------------------------------

             Summary: Investigate an R2DBC client implementation
                 Key: DERBY-7036
                 URL: https://issues.apache.org/jira/browse/DERBY-7036
             Project: Derby
          Issue Type: Improvement
          Components: Network Client
            Reporter: Mark Paluch


As programming models evolve towards functional data access patterns, it would be great to
have a non-blocking, reactive network client implementation for Derby. The advantage of having
a non-blocking I/O layer allows to scale applications by orders of magnitude.

There's an effort named R2DBC to bring Java-based, reactive database access to relational
databases using a standardized API. This ticket is here to start some discussion around whether
you'd be interested to look into this and how we can help.

A few resources to get you started:
 * The project organization can be found [on Github|https://github.com/r2dbc] and contains
the SPI, a client API as well as Postgres implementation and an H2 implementation.
 * An [in-depth talk on the topic|https://www.youtube.com/watch?v=idApf9DMdfk] by Ben Hale
which is basically _the_ introduction you can get.
 * There's a [public mailing list|https://groups.google.com/forum/#!forum/r2dbc] that summarizes
the events and activities around R2DBC.
 * There's the [Spring Data R2DBC project|https://github.com/spring-projects/spring-data-r2dbc]
that provides a good overview of how functional-reactive data access can look like.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message