From Imperative to Reactive Programming
summary
Shows a concrete migration: a blocking JPA/Panache REST endpoint is refactored into async code using Quarkus, a Vert.x reactive MariaDB client and CompletionStage-style composition. Builds DTO/filter/transform methods, replaces direct DB blocking calls with reactive queries, and runs siege load tests: imperative version hits DB pool limits (100 requests, several failures) while the reactive version completes 100 requests with zero failures. Demonstrates manual row-to-entity mapping, a sleep to simulate I/O, and that the refactor works end-to-end.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:15Reactive Systems
- 2:40Reactive Programming
- 5:11What is Reactive Programming
- 7:41Mario Kondo
- 8:24Why Quercus
- 9:34Demo
- 14:58Vertex
- 16:58Reactive
- 19:15Completion Stage
- 21:43Code
- 24:17Static List
- 36:32Leap
related talks
01h 00m"Simply reactive" with Vert.x, Mutiny, Hibernate Reactive and Quarkus
43mMigrating from Imperative to Reactive
01h 00mMigrating from Imperative to Reactive
41mFrom Imperative To Reactive
46mMoving from Imperative to Reactive
53mIntroducing Hibernate Reactive – The first reactive ORM framework
48mReactive for the Impatient
47mReactive Programming - Royal Road or Wrong Turn?