Skip to main content

Jakarta Data 1.0 (under development)

Release supporting Jakarta EE 11

The Jakarta Data specification provides an API for easier data access. A Java developer can split the persistence from the model with several features, such as the ability to compose custom query methods on a Repository interface.

Jakarta Data’s goal is to provide a familiar and consistent, Jakarta-based programming model for data access while still retaining the particular traits of the underlying data store.


  • Increase productivity performing common database operations
  • Rich Object Mapping integrated
  • Define Repositories
public interface Garage extends CrudRepository<Car, Long> {

  List<Car> findByType(CarType type);

  Optional<Car> findByName(String name);


Garage garage;
Car ferrari ="Ferrari").type(CarType.SPORT);;

New features, enhancements or additions

  • The CrudRepository feature
  • Allows pagination on repository with PageableRepository

Minimum Java SE Version

Java SE 17 or higher



Plan Review

The Specification Committee Ballot concluded successfully on 2023-04-03 with the following results.

Representative Representative for: Vote
Kenji Kazumura Fujitsu +1
Emily Jiang, Tom Watson IBM +1
Ed Bratt, Dmitry Kornilov Oracle +1
Andrew Pielage, Petr Aubrecht Payara +1
David Blevins, Jean-Louis Monteiro Tomitribe no vote
Ivar Grimstad EE4J PMC +1
Marcelo Ancelmo, Abraham Marin-Perez Participant Members +1
Werner Keil Committer Members +1
Zhai Luchao Enterprise Members +1
Scott Stark, Scott Marlow Enterprise Members no vote
Total 8

The ballot was run in the mailing list

Back to the top