Reactive SQL: why it matters
summary
The talk explains why non-blocking asynchronous programming matters for increasing deployment density and reducing resource waste, especially in Java microservice architectures that combine networked data sources. It examines options for non-blocking access to relational databases: why traditional JDBC is a counterexample, how to use Vert.x Reactive SQL Client, and how Hibernate Reactive works, comparing their trade-offs in compatibility, performance, flexibility and developer productivity.
AI-written summary · about
chapters (9)
- 0:00Start
- 2:25The changed landscape
- 8:45What is reactive?
- 14:30Why communicate with databases?
- 21:13The connection model
- 25:10How it works
- 28:25Example
- 32:50Demo
- 45:50Conclusion
related talks
48mReactive for the Impatient
55mThe Reactive Revolution
26mReactive Java Programming: a new Asynchronous Database...
52mReactive for the Impatient - A Gentle Intro to Reactive Java
26mBuilding Reactive Application with R2DBC.
51mUnder the Hood of Reactive Data Access
45mShould I migrate to Reactive and how?
24mBringing Reactive Programming to Java and Microservices