Reactive Java Programming: a new Asynchronous Database...
summary
Proposal for a new Java DBA API promises truly non‑blocking SQL access with no user thread ever blocked, built on Java SE 8/9 using CompletionStage and java.util.concurrent.Flow. It defines concrete primitives (row operations, row‑count, row‑publish), a transaction‑completion flag to decide commit vs rollback across future operations, and operation groups for sequencing and parallelism. A prototype runs over JDBC (compiles and demos correctly but is not genuinely async); next step is standardization and vendor drivers.
AI-written summary · about
chapters (12)
- 0:00Introduction and overview
- 1:07Goals of new API
- 3:17Design principles explained
- 6:37Basic API usage with code
- 9:35Data source and session setup
- 11:02Querying and result handling
- 13:17SQL execution and blocking
- 15:01Complex query operations
- 17:14Transaction management
- 21:50Operation groups explained
- 22:33Reactive streams support
- 24:20Wrap-up and resources
related talks
48mReactive SQL: why it matters
46mUsing Java CompletionStage in Asynchronous Programming
38mBest Practices in Reactive Application with Java 1.8 and Play
26mBuilding Reactive Application with R2DBC.
31mJDBC, What Is It Good For?
11mReady for Java 9 - Bridging the Gap Between Database and Stream
41mJava Virtual Threads and Pipelined Database Operations
43mReactive Programming in Java