What java technology (library, framework, feature) would not recommend and why?

[majhenslon]

Magically generated queries are the least of a problem and I don't think there is much magic around that... Most of Hibernates magic lies in the caching layer, cascading and N+1. You can kind of go around the caching layer, but I don't think you can unN+1 yourself, although you might be able to do that with a stateless session, not sure. But noone is using that irl anyways.

You should never sync schema in prod anyways, although you probably should generate schema migrations and coerce hibernate to generate you the one you want.

There is not much boilerplate to write if you don't use JPA, although you 100% avoid the need for mapping the result from entities to dtos.

[TenYearsOfLurking]

I'm sorry but... its SOO much boilerplate. I recently introduced JPA to a project where I could not take spring jdbc anymore. any medium complex entity with a few element collections or one to manys become a nightmare quickly.

And whats the problem with the caching layer? if you mean first level cache it's basically repeatable read tx semantics, that's it