Article 1
Hybrid Persistence in Quarkus: Blocking, Reactive, and Panache Next in One Codebase
This series is based on hands-on migration work, not on a clean-room framework comparison.
Article 2
Hibernate Reactive Without a Rewrite: A Practical Migration Story
If I had followed my first instinct during reactive migration, I probably would have started with easy CRUD.
Article 3
MapStruct in a Reactive World: Keep Mappers Pure
If your mapper calls the database, the mapper is not a mapper anymore.
Article 4
Panache Next Metamodels and Repositories: Where They Actually Help
Panache Next is useful, but not because it magically makes a persistence layer clean.
Article 5
Managed vs Stateless in Panache Reactive: What Actually Changes
The previous article separated repository entry points by operation mode:
Article 6
Stop Migrating CRUD First: Move the Hot Queries First
Most persistence migrations start with CRUD because CRUD is easy to reason about.
Article 7
Reactive Background Jobs, Alerts, and Tests Without Deadlocks
It is possible to migrate request handlers to reactive code and still leave one of the most repetitive parts of the system blocking.