Let’s browse through the surface of the main three reactive database access: Spring Data R2DBC, Hibernate, and jOOQ!
-
Reactive Programming Made Easy
Table of Contents Reactor live templatesDebugging Reactor StreamsNoteworthy inspections for daily needsUnused Publisher valueBlocking call in non-blocking context This article discusses essential features and tools in IntelliJ IDEA for Reactor developers. These include live templates, a dedicated debug mode, and …
-
Backpressure in Reactive Systems
Considering a fast data producer and a slow data consumer, backpressure is the mechanism that “pushes back” on the producer not to be overwhelmed by data.
-
BlockHound: How It Works
BlockHound will transparently instrument the JVM classes and intercept blocking calls (e.g., IO) if they are performed from threads marked as “non-blocking operations only” (ie. threads implementing Reactor’s NonBlocking marker interface, like those started by Schedulers.parallel()).
If and when this happens (but remember, this should never happen!), an error will be thrown.