Full Steam Ahead, R2DBC!
summary
R2DBC is an open JVM spec (born 2017) offering end-to-end non-blocking SQL access; spec R2DBC 0.8 GA and drivers exist for Postgres, two MySQLs, MariaDB, Spanner, SAP HANA, with Oracle and DB2 announced. It exposes a minimal SPI (connection factory, statement, result, row), a standardized URL, categorized SQL exceptions, batching and streaming BLOB/Clob support, and tooling like R2DBC proxy and pools. Spring integration provides DatabaseClient, reactive transactions, and Spring Data R2DBC (1.2 adds entity callbacks, auditing); it reduces JVM thread congestion but does not remove DB-side limits.
AI-written summary · about
chapters (15)
- 0:00Introduction and welcome
- 1:08What is R2DBC
- 2:12Reactive programming explained
- 9:31Non-blocking SQL persistence challenges
- 15:50Birth of R2DBC standard
- 20:27R2DBC design principles
- 24:43R2DBC 0.8 features
- 28:41R2DBC ecosystem overview
- 31:51R2DBC benefits and trade-offs
- 32:52Spring Framework and R2DBC
- 37:13Using Spring Database Client
- 39:44Spring Data R2DBC introduction
- 44:40Spring Data R2DBC 1.2 updates
- 47:11Future of Spring Data R2DBC
- 48:13Closing and Q&A
related talks
34mR2DBC = R2D2 + JDBC (Well, Almost...)
48mReactive Relational Database Connectivity
37mReactive Relational Database Connectivity using R2DBC
49mSpring Data R2DBC. Explaining It One Last Time
56mGetting Reactive with Relational Databases & R2DBC
26mBuilding Reactive Application with R2DBC.
59mOn the way to Reactive
48mGetting Reactive with Relational Databases and R2DBC