What Is Jakarta Data?

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 newer Jakarta 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. 

For instance Apache DeltaSpike’s JPA module provides a way to use the repository pattern with Jakarta Persistence. Much like Spring Data, DeltaSpike allows for powerful data abstraction over Jakarta Persistence for Jakarta EE applications. However, this and other similar libraries are not part of the Jakarta EE Platform. And this is where Jakarta Data comes in.

The Need For A Unified API

Jakarta Data is currently a specification proposal led by Otavio Santana, with the goal of unifying all these data abstractions under a single specification, and consequently, API. With Jakarta Data, both SQL and NoSQL data access will come under a single, unified set of APIs that provide much modern paradigms of data access like the aforementioned repository pattern and cloud data access. In a cloud native development era, microservices can access data in a myriad of ways, and this specification aims to standardize all these data access options under a single specification. 

As the current evolution of Jakarta EE continues, a specification such as Jakarta Data will help solidify the platform as a first class choice for developing modern, cloud native applications. New microservices focused frameworks come with such convenience APIs built-in, and as such make them much more appealing to developers. Jakarta Data will be a great addition to the already rich set of specifications that make up the Jakarta EE Platform.

You can (and should at least take a look) make suggestions to the process in this sheet as it is in the process of gathering feedback. As Jakarta EE experts, we will keep you updated with the progress of this specification and eventually help you learn all there is to using it when it is finally available. 

What to find out more about Jakarta EE specifications? Check out our previous fact sheets:

Comments (0)

Post a comment

Your email address will not be published. Required fields are marked *

Payara needs the contact information you provide to us to contact you about our products and services. You may unsubscribe from these communications at any time. For information on how to unsubscribe, as well as our privacy practices and commitment to protecting your privacy, please review our Legal & Privacy Policy.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Related Posts

Illustration showing the Payara logo and the words “New Release” in large orange and white text, next to a stylized laptop screen displaying the Payara Server admin console with dark blue and orange interface elements. 3 minutes
Product News

What’s New in the January 2026 Payara Platform Release?

As we begin 2026, we’re pleased to announce new releases across all Payara Platform editions this January: Payara Platform […]

Blog 15 Step Journey 4 minutes
Jakarta EE

Building a Modern Enterprise App with Payara: A 15-Step Journey 

Learning Jakarta EE can sometimes feel like solving a puzzle. You have JPA, CDI, REST, Security, and Docker... but how do they all fit together in a real-world scenario? 

Cut Jakarta EE Startup Times from Seconds to Milliseconds with CRaC 8 minutes
Jakarta EE

Cut Jakarta EE Startup Times from Seconds to Milliseconds with CRaC 

Jakarta EE applications can take anywhere from several seconds to over a minute to start, depending on their size […]