Reactive Relational Database Connectivity
summary
R2DBC presents a concrete reactive driver spec that is non-blocking to the wire, uses reactive streams types, and requires new drivers to implement database wire protocols rather than wrap JDBC. The SPI intentionally stays tiny — minimal SPI for drivers — so higher-level clients (r2dbc-client, Spring Data R2DBC) provide humane APIs, transactions, batching, zero‑indexed positional and named bindings, and connection URL parsing. Release 0.8.0‑M8 exists with H2, Postgres, MSSQL and MySQL implementations; RC1 and GA are targeted next.
AI-written summary · about
chapters (18)
- 0:00Introduction to reactive
- 1:30Fundamentals of reactive
- 3:09Reactive streams and flow
- 6:00Database access barriers
- 8:03R2DBC design principles
- 9:27Fixing JDBC's shortcomings
- 11:33Connection and statements
- 13:55Data binding and execution
- 16:27Mapping results
- 20:25Executing inserts
- 24:12Reactive transactions
- 26:56Humane API clients
- 30:16Spring Data integration
- 33:09Connection URLs and pooling
- 37:04Current state of R2DBC
- 39:28Observability and community
- 41:15JDBC limitations
- 43:41Future goals and resources
related talks
34mR2DBC = R2D2 + JDBC (Well, Almost...)
37mReactive Relational Database Connectivity using R2DBC
56mGetting Reactive with Relational Databases & R2DBC
50mFull Steam Ahead, R2DBC!
26mBuilding Reactive Application with R2DBC.
48mGetting Reactive with Relational Databases and R2DBC
01mGetting Reactive with Relational Databases and R2DBC
49mSpring Data R2DBC. Explaining It One Last Time