4 ms·
I don't disagree with your conclusion. But your comment communicates no argument against Spring and how the trade-offs it makes make it a poor option for new pr
by mixedCase 6y ago
I don't disagree with your conclusion. But your comment communicates no argument against Spring and how the trade-offs it makes make it a poor option for new projects.
- karmakaze 6y agoAnyone 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.
- johnnycerberus 6y agoWhat's the alternative?
- karmakaze 6y agoSeveral are mentioned in comments of this thread. Search results show too many old ones. 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/guide/ https://micronaut-projects.github.io/micronaut-sql/latest/gu...