Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jnosql-dev] [nosql-dev] The Jakarta NoSQL's future

Hey Otávio:

I don't understand why having a second implementation is a reason not to include Jakarta NoSQL on the platform.  If you look at the individual specs, most of them only have one implementation listed.

I believe we should remain on Jakarta EE so that we have Jakarta Data, Jakarta NoSQL and Jakarta Persistence all together.  From what I understand, Jakarta EE 11 is scheduled for 1Q2024.

All the best,


On Wed, Jan 11, 2023 at 4:35 AM Otavio Santana <otaviopolianasantana@xxxxxxxxx> wrote:

Following the previous feedback from the program committee:

We don’t have a problem with the spec exploring this direction, but we currently have no interest in incorporating this in any profile or the platform. We’d also want to see interest and active work in a second implementation before this spec would be proposed final.

They don’t plan to move it forward as part of the Jakarta EE platform; on the other hand, we have Jakarta Data as a WIP specification that takes considerable effort to make happen.

Given this scenario, what do you think the best strategy for Jakarta NoSQL is?

I thought of some options:

  • Think about moving to the Eclipse Microprofile side
  • Returns the efforts to focus on JNoSQL (as a library that implements Jakarta Data) and hold Jakarta NoSQL for a while.
  • Find a second implementation for Jakarta NoSQL (which company?)

Another option, I’m open to suggestions.

Otávio Santana
nosql-dev mailing list
To unsubscribe from this list, visit

Code, TestWrite, Cycle, Run, Drink, Sleep ... Repeat
Lead Java Queue Editor, InfoQ

Laissez Les Bon Temps Rouler

Back to the top