[CONJ-688] Non-blocking client implementation using standardized API for scalable data access Created: 2019-02-23  Updated: 2020-03-06  Resolved: 2020-03-06

Status: Closed
Project: MariaDB Connector/J
Component/s: Other
Affects Version/s: None
Fix Version/s: N/A

Type: Epic Priority: Major
Reporter: Mark Paluch Assignee: Diego Dupin
Resolution: Fixed Votes: 1
Labels: None

Epic Name: Investigate R2DBC Client Implementation

 Description   

As programming models evolve towards functional data access patterns, it would be great to have a non-blocking, reactive network client implementation for MariaDB. 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 and contains the SPI, a client API as well as Postgres and Microsoft SQL Server implementations.
  • An in-depth talk on the topic by Ben Hale which is basically the introduction you can get.
  • There's a public mailing list that summarizes the events and activities around R2DBC.
  • There's the Spring Data R2DBC project that provides a good overview of how functional-reactive data access can look like.


 Comments   
Comment by Diego Dupin [ 2020-03-06 ]

Here it is : https://github.com/mariadb-corporation/mariadb-connector-r2dbc

Generated at Thu Feb 08 03:17:35 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.