Question: Spring with exposed or jpa?

[gunslingor]

I'm looking at an old spring boot kotlin grade app I wrote and I am rebuilding... trying to understand why I used exposed instead of jpa, which I suspect could also be kotlin.

What do you think, which should I have used or is it arbitrary?

Any input appreciated.

[heli-os]

Hi @gunslingor 😆

i am an engineer developing web server application using Java/Kotlin and SpringBoot. At that time, DataSource Access used JPA and QueryDSL a lot.

I do a lot of clean architecture development based on Kotlin + JPA, but I felt some inconvenience.

1. Doesn't work properly without plugin(because kotlin class and function are final by default and does not have default constructor)
2. Entities cannot be used as data classes.
3. Entity is not suitable for handling immutable objects, so we have to use var not val
4. when developing with a domain-oriented clean architecture, we cannot use the powerful features of JPA at all. if using JPA, Simply map code-level logical relationships and easily send queries. But it can be done more easily with spring-data-jdbc or other ORM.

In addition, when developing with a clean architecture, it is difficult to comfortably use JPA's Persistence Layer primary cache function including dirty-checking.

So I'm using spring-data-jdbc + jooq, and now I'm using Exposed. It is not the answer.

This solution is also inconvenient, but I've been looking for a more lightweight library.