I find that jOOQ (java) solves all that for me. Very happy to not have and ORM on our stack for many years. I believe that the interaction with the database i

I find that jOOQ (java) solves all that for me. Very happy to not have and ORM on our stack for many years. I believe that the interaction with the database is just about the most important part of code that you need to rely on. We have had messy data written to the database due to misused or misconfigured ORM (perfomance issues, bad orphan handling, session state problems, overflown sequences, to list a few) and decided that we should not rely on all devs touching that code to be experts in the ORM api to avoid the pitfalls, we rather our devs be expert in SQL. Never had any of them complain about mapping using something like jOOQ. Type checking and composability are also built in.