In Relation To

The first Beta of Hibernate ORM 6.0 has just been released.

We had a few main focuses for this Beta:

Hibernate ORM 6.0 Alpha9 has just been released.

The main design goal for 6.0 is to improve even more Hibernate’s through-put performance. High-load performance testing showed Hibernate’s approach of reading values from ResultSet by name to be its most limiting factor in scaling throughput. At its most basic, 6.0 is all about changing from its old strategy of read-by-name to read-by-position. But that simple goal has a lot of ramifications.

With Alpha9, the APIs are really starting to stabilize which is great.

Hibernate ORM 6.0 Alpha6 has just been released.

The main design goal for 6.0 is to improve even more Hibernate’s through-put performance. High-load performance testing showed Hibernate’s approach of reading values from ResultSet by name to be its most limiting factor in scaling throughput. At its most basic, 6.0 is all about changing from its old strategy of read-by-name to read-by-position. But that simple goal has a lot of ramifications.

This Alpha6 release includes:

We are excited to announce the release of Hibernate ORM 6.0 Alpha5.

The main design goal for 6.0 is to improve even more Hibernate’s through-put performance. High-load performance testing showed that Hibernate’s approach of reading values from ResultSet by name to be its most limiting factor in scaling through-put. At its most basic, 6.0 is all about changing from its old strategy of read-by-name to read-by-position. But that simple goal has a lot of ramifications.

We have come really far, but still it is an Alpha, so there is still plenty more to do.

We are excited to announce the release of Hibernate ORM 6.0 Alpha4.

The main design goal for 6.0 is to improve even more Hibernate’s through-put performance. High-load performance testing showed that Hibernate’s approach of reading values from ResultSet by name to be its most limiting factor in scaling through-put. At its most basic, 6.0 is all about changing from its old strategy of read-by-name to read-by-position. But that simple goal has a lot of ramifications.

We have come really far, but still it is an Alpha, so there is still plenty more to do.

We are excited to announce the release of 6.0 Alpha3.

The main design goal for 6.0 is to improve even more Hibernate’s through-put performance. High-load performance testing showed that Hibernate’s approach of reading values from ResultSet by name to be its most limiting factor in scaling through-put. At its most basic, 6.0 is all about changing from its old strategy of read-by-name to read-by-position. But that simple goal has a lot of ramifications.

We have come really far, but still it is an Alpha, so there is still plenty more to do.

Generally speaking, an ORM solution will have support for creating a lazy proxy for an entity based on its identifier value. Historically Hibernate supported generating these proxies using Java’s proxy feature (see java.lang.reflect.Proxy). Hibernate now supports proxying an entity using bytecode enhancement.

We are excited to announce the release of 6.0 Alpha1.

The main design goal for 6.0 is to improve even more Hibernate’s through-put performance. High-load performance testing showed that Hibernate’s approach of reading values from ResultSet by name to be its most limiting factor in scaling through-put. At its most basic, 6.0 is all about changing from its old strategy of read-by-name to read-by-position. But that simple goal has a lot of ramifications.

We have come really far, but still it is an Alpha, so there is still plenty more to do. Each section below breaks down what works, what does not work, what is not yet implemented.

Hibernate ORM version 5.3.0.Final has just been released.

This is the second CR release for the Hibernate ORM 5.3 family. 5.3 represents a JPA 2.2 compatible version on top of 5.2.

CR1 was work done to verify against the JPA 2.2 TCK. CR2 was, partially, work done based on the efforts of WildFly to certify against the full EE TCK, which has additional JPA-related tests.

The remainder of CR2 work mainly focused on binary compatibility for 5.3 with 5.1 and 5.2. Most of that work has been done under HHH-12424 and its sub-tasks. It was this work mainly that caused the delays in getting CR2 released. I apologize for that delay, but this was deemed a very important task.