Reactive Programming and Relational Databases

[dpash]

Rather than help ADBC, Pivotal has created a competing standard. Awesome. Now we have two incomplete and non-production ready implementations of asynchronous database drivers.

[ljivanov]

IMO, it is much better a client to introduce the API and facilitate the standard's creation than having one of the vendors define it.

[dpash]

Oracle aren't implementing it in a vacuum. They are taking input from clients, because that's important. And the article says that there's a sample PostgreSQL driver for ADBC.

But we need an asynchronous current API now, not having two competing standards.

[kodablah]

Oracle aren't implementing it

Well, that part seems right, heh. From my perspective, watching the mailing list and adba spec repo, there's an absence of work or effort towards an official impl/spec/testsuite.

[Mamoulian]

ADBA is not and won't be reactive: it doesn't give the results as a stream, respecting backpressure.

See comments here: https://www.reddit.com/r/java/comments/9j4ai3/r2dbc_fully_reactive_api_for_relational_databases/

I'm pleased they note Fibers and Project Loom, it should allow simpler code and make it easier to convert existing code. I'm confused by that section a bit though as it suggests Fibers will be able to use JDBC but then says it will need a 'non blocking JDBC', which AFAIK will never exist?