Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [nosql-dev] Questions about use of Jakarta NoSQL on Jakarta EE 11 implementations...
Hello Scott, how are you?



1.

It is managed by the NoSQL native driver, where each NoSQL database has its way of doing and balancing between the available nodes.

2.

We don't have the plan to integrate with JTA in the first version; mainly, as you said, not the majority of the databases have ACID support.

3.

The current Jakarta NoSQL API supports the basic behavior allowing extension for particular behavior for each NoSQL database. Thus, the API will stay the same because it is around the basic behavior each NoSQL database might have.

We could see several Elasticsearch breaking changes without breaking the Spec API, which also happened with Cassandra API for a few cases.

Our next move will be to upgrade ArangoDB as well, where it will have to break changes on its driver side, but it won't change the spec API.




On Fri, Jun 9, 2023 at 5:01 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:
Hi,

During the Monthly Platform call this week (June 6, 2023) I asked a few questions about what users of Jakarta NoSQL could expect with regard to their Jakarta EE 11 deployments that I would like to echo here and create tracking issues as needed.

My questions are mostly about how NoSQL integrates with Jakarta EE 11 implementations.

1.  Will the NoSQL database server connections be considered managed by the underlying EE implementation in the same way they are for traditional javax.sql.DataSource?  Or are the NoSQL connections independently managed by the NoSQL native driver?

2.  Will the NoSQL database server connections be enlisted as ACID resources into JTA transactions?  Not many NoSQL databases support ACID but I am asking more to understand the model that will be expected in EE 11 applications that do rely on JTA transactions.

3.  I'm trying to wrap my head around the life cycle impact of including Jakarta NoSQL in Jakarta EE 11 and which parts of SPEC/API [2], Mapping APIs [3], integrations [4] would be included in an EE release.  Working backwards on asking my main question, how would we ensure that NoSQL database integrations [4] for Jakarta NoSQL 1.0 continue to work for Jakarta EE 11 applications?  For example, I see that currently OrientDB 3.2.16 is supported but there will be many different versions of OrientDB (both past and future releases) and since EE 11 application deployments will likely expect to work for many years, how can users expect to use new (or older) versions of [4] with their EE 11 apps?

Thanks,
Scott

[3] Mapping APIs for each NoSQL type https://github.com/eclipse/jnosql
[4] Implementations of NoSQL database integration https://github.com/eclipse/jnosql-databases
_______________________________________________
nosql-dev mailing list
nosql-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/nosql-dev


--

Thanks a lot,

Twitter | Linkedin | Youtube

Back to the top