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.
We just published two bugfix releases for Hibernate Search:
5.11.4.Final and 5.10.8.Final.
These releases mainly upgrade Hibernate Search to the latest compatible Hibernate ORM versions
and fix one issue with the Elasticsearch integration.
Hibernate libraries can be used with many frameworks,
and we’re striving to make sure that everyone gets their fair share of Hibernate goodness.
So with the recent announcement of the first release candidate of Quarkus,
the "supersonic, subatomic" Java stack,
it’s worth mentioning that Hibernate ORM, Search and Validator are already included in Quarkus.
Hibernate Search in particular, the library adding the power of full-text search to your ORM-based application,
is included in its most recent version (6.0.0.Beta2), which adds first-class compatibility with Elasticsearch.
Let’s take this Quarkus release as an opportunity to have a closer look at Hibernate Search 6,
and how it can be used in Quarkus.