Spring with Hibernate ORM, or Exposed?

# spring

[Christopher Hübner]

Spring with Hibernate ORM, or Exposed?

[hho]

Anything but Hibernate... Spring with jOOQ is also nice.

[hennilu]

Working with Hibernate and we have tried once to move away.

Went for Ktorm, but it seems to be unmaintained except for someone saying in GH Issues that the maintainers are planning a new release.

Now we’re considering several alternatives combined with Spring:
• jOOQ
• Exposed (DSL, not DAO)
• Spring Data JPA + nativeQueries
• The new JdbcClient that came with Spring Framework 6.1.x

[Saharath Kleips]

We moved our spring apps from data jpa to jooq recently and are quite happy with the level of flexibility and safety it gives us. I’ve used exposed for some small projects and have found it nice, but haven’t used it in a larger production setting and don’t really plan to since our team is happy with jooq.

[Jacob]

I don't think hibernate with it's massive amount of mutable state fits with the more functional style typical of kotlin developers

[Jacob]

Also hibernate team themselves don't seem to be spring data jpa fans.

[Jacob]

https://docs.jboss.org/hibernate/orm/6.4/introduction/html_single/Hibernate_Introduction.html#architecture

[hantsy]

We use Spring/Kotlin Coroutines, R2dbc/Spring Data R2dbc, jOOQ

[hantsy]

jOOQ is good match with Kotlin, and codegen can generate Kotlin metadata