Jakarta Query: Unifying Queries in a Polyglot Persistence World, the News on Jakarta EE 12 M2

As software architectures grow more complex, persistence ceases to be a purely technical concern and becomes an architectural one. Modern systems rarely rely on a single database or a single data model. Instead, they adopt polyglot persistence, choosing different storage technologies depending on scalability needs, access patterns, and domain boundaries. Relational databases remain essential, but they increasingly coexist with document stores, key-value databases, and other non-relational systems. This reality has already reshaped the Jakarta ecosystem. Specifications like Jakarta NoSQL and Jakarta Data emerged to acknowledge that persistence is no longer synonymous with ORM. With Jakarta EE 12 , another important piece joins the picture: Jakarta Query , a new specification designed to unify how Java developers query data across persistence technologies.