Home Programming News Bye Bye Hibernate – Discovering options to Hibernate in Kotlin | Weblog | bol.com

Bye Bye Hibernate – Discovering options to Hibernate in Kotlin | Weblog | bol.com

Bye Bye Hibernate – Discovering options to Hibernate in Kotlin | Weblog | bol.com


We’re additionally capable of give JOOQ our area mannequin and let it routinely determine the mapping from the question into the area mannequin. JOOQ can do routinely match this primarily based on present JPA annotations within the area mannequin, the “best-matching constructor” or a customized mapper you present your self.

In our venture we solely used the metadata constants, whereas JOOQ has extra to supply. JOOQ additionally generates DAO’s as an illustration. We investigated implementing the generated DAO’s in our venture, however they included default strategies that we thought-about not helpful. As an example, a technique was generated to lookup experiments by (alphabetic) vary of speculation. It appears this ‘choose by vary’ is generated for all fields and creates muddle.

Moreover, the generated DAO code doesn’t appear to take indexes into consideration. A lot of the queries would result in a full desk scan in the event that they have been used, which may closely impression efficiency. We see room for enchancment right here: JOOQ may use the indexes as an indicator of whether or not there’s any use case for the code and go away a extra concise DAO. This is without doubt one of the causes we focussed our efforts on utilizing the metadata constants.

Our conclusion about JOOQ:

  • JOOQ’s documentation is elaborate and makes the framework straightforward to make use of. Particularly if in case you have an present database schema or plan on utilizing a database migration instrument like Flyway.
  • The metadata constants generally is a good type-safe question implementation, primarily based in your present database. Due to this we have been capable of implement JOOQ with minimal boilerplate code relating to mappings to the info entry layer.
  • JOOQ is actively maintained with month-to-month releases and is essentially the most used ORM framework after Hibernate inside bol.com.
  • One further notice is that JOOQ has a number of paid variations, that supply a wider vary of supported database dialects and extra options. Our database sort, Postgres, amongst different widespread ones are supported within the open-source model. In style databases like Oracle and SQL Server are solely supported within the paid variations.

Noteworthy point out: Krush

The additional added boilerplate in mapping between the area mannequin and the desk mannequin with Uncovered and Ktorm inspired us to search for an alternate, onto which we encountered Krush.

Krush is predicated on Uncovered and claims to be “a light-weight persistence layer for Kotlin primarily based on Uncovered SQL DSL.”. It removes the necessity for boilerplate mappings by including again JPA annotations to the area mannequin, which we’re used to from Hibernate.

Sadly, there is no such thing as a utilization of this framework inside bol.com and on GitHub the neighborhood additionally appears too small to contemplate for utilization in manufacturing. Due to this, we concluded that we’d not go to the extent of testing its behaviour. As a substitute, we are going to give Krush an in depth look infrequently to see the way it develops.

Noteworthy point out: Spring JDBC

You may not want all of the complexity that Hibernate/JPA has to supply. Switching to a distinct ORM framework altogether might be heavy as properly. What if there would simply be a less complicated various within the ecosystem you might be already utilizing? One such various is out there in all Spring initiatives: Spring JDBC!

Spring JDBC will give you a extra low-level method, primarily based on JDBC immediately. This generally is a good method for smaller initiatives that need to write native queries.


Becoming a member of forces within the bol.com hackathon to analyze Hibernate options in Kotlin was enjoyable and we discovered loads in regards to the accessible options on the market. Our greatest studying is that there are 4 main methods of approaching the ORM world:

  • Database schema first, the method that JOOQ takes.
  • SQL DSL first, the method that Uncovered and KTORM take.
  • JPA annotations first, the method that Hibernate and Krush take.
  • Low degree, the method that Spring JDBC takes.

All these approaches include their very own set of benefits and downsides. For our use case JOOQ might be a substitute for Hibernate in our Kotlin initiatives. JOOQ would enable us to modify ORM frameworks with minimal adjustments and most type-safety, whereas protecting boilerplate at a minimal. The neighborhood and utilization additionally appear ok to undertake the framework for utilization inside a manufacturing surroundings.

It is very important notice that doing a migration from one ORM framework to a different is a heavy course of that wants devoted time to make it work, together with efficiency checks. Hibernate generally is a legitimate ORM framework alternative in a venture. We hope that you’re now extra conscious of among the different frameworks you possibly can select from and the way they work.

1 In the course of the hackathon the venture crew additionally reserved a small period of time to analyze options for Hibernate Envers. Utilizing a distinct ORM framework then Hibernate can pose a problem if you nonetheless need to have such out of the field auditing accessible, as Hibernate Envers can solely be utilized in mixture with Hibernate itself. The conclusion of the small investigation was that Javers promised to be an acceptable various, though this framework appears solely maintained by one individual. Alternatively, you may use a extra low-level method through the use of database triggers that audit and log adjustments.

2 Some time in the past Sander spent hours attempting to debug issues that have been associated to utilizing knowledge lessons with Hibernate, which ultimately led him to the listed article and repository. An instance of such an issue is that the appliance tried to delete an object from the database, however by means of Hibernates magic underneath the hood the article was recreated after the deletion in the identical transaction, leading to no object being deleted. Utilizing one of the best practices from the listed article led to constant outcomes.



Please enter your comment!
Please enter your name here