Earlier today, the Eclipse Foundation together with its vendor members, partners and community has announced the release of Jakarta EE 11, the latest version of its enterprise Java platform. Building on the Core Profile (Dec 2024) and Web Profile (Mar 2025), this release brings powerful new features aimed at boosting developer productivity and simplifying cloud-native development.

Traditionally, enterprises stored their SQL data in relational database management systems (RDBMS). However, the strict and rigid SQL data format is not always fit for purpose...

This has led to the rise of schemaless databases and NoSQL. The distributed, non-relational model of NoSQL database technology made it the almost perfect choice for companies like Twitter, Google and Facebook that had amassed massive datasets from their web applications. 

But is it right for your enterprise? And will it work with Jakarta EE?

The defacto way of accessing relational data in a Jakarta EE application is through the use of the Jakarta Persistence API. For NoSQL data access, one can now use the much newerJakarta NoSQL API. Jakarta Persistence especially has worked quite well and been serving its purpose with both its support for native queries, JPQL and Criteria queries. However, modern data access paradigms have meant having to pull in third party libraries to enjoy some more abstractions.