Earlier quoted context omitted.
Anyone with sufficient experience with JPQL and Hibernate will realize their limits and how poorly it works in the latency sensitive transactions we want now. Spring and Hibernate were designed to cache domain 'entities' and manage their dirty state client-side as an optimization. Any time you go want to go near the EntityManager you're hitting this impedance mismatch.
What's the alternative?
As a short-list sampling, a Micronaut SQL guide[0] lists the following:
JDBC
Hibernate
JAsync SQL
jOOQ
Jdbi
Reactive MySQL Client
Reactive Postgres Client
I myself chose JDBI for more recent projects using Java/Kotlin.[0] https://micronaut-projects.github.io/micronaut-sql/latest/gu...