# Quarkus Insights #250: What's New with Quarkus Data

DevFeed: [Quarkus Insights #250: What's New with Quarkus Data](<https://devfeed.tech/articles/quarkus-insights-250-what-s-new-with-quarkus-data-43878.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-insights-250-quarkus-data/>)

Author: James Cobb (https://twitter.com/insectengine)

Published: 2026-06-08T00:00:00Z

Content type: release

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Object-relational mapping](<https://devfeed.tech/topics/orm.md>), [Persistence](<https://devfeed.tech/topics/persistence.md>), [reactive](<https://devfeed.tech/topics/reactive.md>), [MongoDB](<https://devfeed.tech/topics/mongodb.md>)

Tags: [hibernate](<https://devfeed.tech/tags/hibernate.md>), [mongodb](<https://devfeed.tech/tags/mongodb.md>), [orm](<https://devfeed.tech/tags/orm.md>), [persistence](<https://devfeed.tech/tags/persistence.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [reactive](<https://devfeed.tech/tags/reactive.md>), [what-s-new](<https://devfeed.tech/tags/what-s-new.md>)

## AI overview

Episode 250 of Quarkus Insights explains the evolution of Panache into Quarkus Data. It covers the rationale for the rename, the effort to unify data technologies and execution styles, Panache's productivity features, and limitations the redesign aims to address.

## Source excerpt

This summary was generated using AI, reviewed by humans - watch the video for the full story. Quarkus Insights #250: What''s New with Quarkus Data Episode 250 of Quarkus Insights focused on one of the longer-running efforts in the Quarkus data layer: the work formerly known as "Panache 2", then "Panache Next", and now Quarkus Data. Stephane Épardaud joined the show to explain why the rename matters, what problems this new API is trying to solve, and how it brings together ideas from Jakarta Data, Hibernate ORM, Hibernate Reactive, and eventually MongoDB under a more consistent programming model. Why "Quarkus Data"? The first announcement was the name itself. What started as an internal evolution of Panache has grown into a broader data-layer effort, so the team wanted a name that is easier to discover and better aligned with the problem space. Steph explained that "Panache" is memorable if you already know Quarkus, but less obvious for users browsing extensions on code.quarkus.io. "Quarkus Data" is more descriptive and mirrors earlier naming simplifications such as the move to Quarkus REST. The rename also reflects scope. This is no longer just a new Panache flavor for one backend. The goal is a common umbrella for multiple data technologies and execution styles. What Panache Got Right Before getting into the redesign, the discussion acknowledged why Panache became popular in the first place. Panache made live coding and rapid development much easier by removing a lot of repetitive persistence code. With a typical entity extending a Panache base type, developers got: Automatic IDs Public fields instead of boilerplate getters and setters Instance methods such as persist() and delete() Convenient query helpers like find(), count(), delete(), and findById() Shortened query syntax instead of always writing full HQL/JPQL A small, discoverable API surface That simplicity is still a major design goal. Quarkus Data is not trying to abandon the productivity benefits of Panac