hypersistence-utils VS FlexyPool

Unfortunately, you cannot smoothly wrap the sequence-based IDs with value objects. There are solutions, but they are rather cumbersome. I left the proposal to the Hibernate types project of adding support to this feature. You’ve already seen the benefits of user-defined types. So, you can rate up my issue to make it more popular.

The Hibernate Types project.

Spring Data / Hibernate does not support JSON fields out-of-the-box, but there is a library that provides custom types for the most common database systems: hibernate-types. This is a fantastic open source library, please support it!

I will blog about it in the following months. So far, I managed to add a new Hibernate Types module for Hibernate 6 and released the 2.15 version.

For current work, hibernate-types works great to support json/jsonb.

Complex DB structures are not a problem. You can map any database type you want: JSON, HStore, Ranges, Inet, as I did in this hypernate-types project.

I am using the Hibernate Types library for custom Hibernate types.

However, PostgreSQL caches the sequences per-connection (different from Oracle that caches in the instance shared memory). Sequences can be a bottleneck in case of a storm where all have a cold cache, and here is a workaround. Note that re-connecting in PostgreSQL is expensive for many reasons and better fixt that with a connection pool that is not too dynamic (if you need this, you should have a look at FlexiPool)

FlexyPool