Reactive Relational Database Connectivity using R2DBC
summary
The talk explains R2DBC (Reactive Relational Database Connectivity) as a non-blocking alternative to JDBC for accessing relational databases in cloud and high-concurrency environments. It covers available R2DBC drivers and framework support (Spring Web MVC vs Spring WebFlux), shows how to implement R2DBC, and presents measured comparisons of resource usage, throughput, and response times between R2DBC and JDBC to evaluate whether switching is worthwhile.
AI-written summary · about
chapters (7)
- 0:00R2DBC introduction
- 3:30Blocking vs reactive access
- 10:00JDBC overhead costs
- 15:00Spring Data R2DBC
- 20:00Benchmarking reactive vs blocking
- 25:00Reactive client benefits
- 30:00R2DBC future & Q&A
related talks
34mR2DBC = R2D2 + JDBC (Well, Almost...)
48mReactive Relational Database Connectivity
01h 10mWhy We Decided to Move to R2DBC and How That Ended
56mGetting Reactive with Relational Databases & 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