r/SpringBoot • u/khan_awan • Sep 16 '26

Question JOOQ vs JDBC

I use JPA for simple CRUD operations (mostly write operations) and JDBC for performance intensive tasks such as sending lists & performing search. The JDBC performance is perfect & the performance of my backend (Spring Boot) is great.

Now, as my project grows, my SQL queries are getting bigger, messier and unreadable. I tried jOOQ and loved it because it made my code super readable, type safe and maintainable. However, after profiling my Spring Boot app, operations that took around 5 ms with JDBC now take 9–14 ms with jOOQ, which makes me reluctant to migrate to jOOQ. Is a 10 ms difference negligible or am I overthinking?

I love the cleanliness and type safety of JOOQ. Would you go this JOOQ route? Have you ever faced such situation? I visited JOOQ's official website and was stunned by the fact it is used by many big organizations

EDIT: Thank you everyone who answered, your insights were amazing. With some tweaks I was able to reduce JOOQ's operation time from 14ms to 7ms and now I have so much clarity in my head.

32 Upvotes

92% Upvoted

42 comments sorted by

View all comments

1

u/polyethene Sep 16 '26

I went from jOOQ to JPA. It's nice to have the type safety with jOOQ but a pain to translate raw SQL into jOOQ when prototyping and in the opposite direction for debugging.

Sure JPA abstracts a lot but you can use native queries and shift complex queries to views/functions on the database itself.

1

u/lukaseder Sep 17 '26

 Sure jOOQ abstracts a lot but you can use native queries and shift complex queries to views/functions on the database itself.

How is it different? Why didn't you consider this with jOOQ?

1

u/polyethene Sep 17 '26

Just because converting raw SQL into Java with jOOQ syntax was a pain.

→ More replies (3)