Tags
Authors
We’re now seeing a lot of interest in Jakarta Data, along with very positive reactions from the people who’ve already tried it out.
I’m afraid I missed the news that Hibernate 6.6 is now available in Quarkus, and so I’ve been slow of the mark in letting everyone know that Hibernate Data Repositories, our implementation of Jakarta Data, is now fully integrated with Quarkus. 🎉🎉
To start writing repositories, all you need to add is:
We have talked about this Quarkus “Panache” thing recently in this blog, but we should probably get into a little more detail about what it is, and why it matters.
First thing, to clarify, we’re talking about “Hibernate ORM with Panache”, which roughly means we’re talking about a flamboyant and reckless flavour of Hibernate ORM.
This means two essential things:
-
It’s the full Hibernate ORM, not anything less
-
But it looks different to what you’re used to
-
You can fallback at any time and even mix vanilla JPA and Panache
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.
