Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jnosql-dev] Time to think about the API shape.
Yes, both will be the RI.

On Thu, Jun 7, 2018 at 11:48 AM Lucas Furlaneto <lucasfurlaneto.s@xxxxxxxxx> wrote:
JNoSQL is very stable and with a lot of features. 

While the EE4J process is not ready, we can start to think about the API, TCK and the spec. 

And about the reference implementation? We will use Artemis and Diana?

Lucas Furlaneto


Em qui, 7 de jun de 2018 às 07:38, Otávio Gonçalves de Santana <otaviopolianasantana@xxxxxxxxx> escreveu:


On Thu, Jun 7, 2018 at 12:27 AM Fernando Boaglio <fernando@xxxxxxxxxxx> wrote:
ok, here we go =)

1 - How will we handle JNoSQL version in the API ?

Once the spec is done, we cannot break version anymore, however, once we need to define things such as the package name. So, we can put any break changes in the releases. 

2 - This compatibility test is regarding db drivers versions ?

No, initially we don't care about the driver version once they have compatibility with the JNoSQL API, that why we have the TCK. The provider still free to create particular behavior, that is the beauty in NoSQL the diversity! 

3 - Metrics is a great idea, but how intrusive is to use it ?
The API is ready, we just need to integrate it, however, IMHO this integration should be outside of the JNoSQL spec. 

4 - (not really related to this email but...) - MongoDB 4 will handle transactions among its documents even in different collections, is it something like this planned in the JNoSQL roadmap ?

Yeahp, that is a nice feature from MongoDB, however, it just belongs to MongoDB. We can create an extension to use this feature to MongoDB. 


On Wed, Jun 6, 2018 at 8:21 PM, Otávio Gonçalves de Santana <otaviopolianasantana@xxxxxxxxx> wrote:


Hello everyone, there text query to NoSQL bring to us a new perspective to project and we have a lot of cool features at Eclipse JNoSQL.
We have the release planned:

And the API is pretty stable.

IMHO: The next move is to make and think the Shape of the API, the spec.
One thing that I have in my mind follows an Eclipse Microprofile project such as Metrics:  https://github.com/eclipse/microprofile-metrics

So, a new Github repository that has three modules:

  • API: that just have the interfaces with Javadoc
  • TCK: with to the compatibility test
  • spec: that spec documentation writing in asciidoc


The process at EE4J still WIP, however, if we keep it closest to the other candidate to EE4J we'll be in a good shape.

Thoughts.

--
Otávio Gonçalves de Santana

_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jnosql-dev




--

Fernando Boaglio

│◦└̅┘◦ ◦ ﴾̭▒̭̊▒̭̊﴿ ﴾̭▓̭̊▓̭̊﴿ ﴾̭░̭̊░̭̊﴿ ◦ ◦ (͡ < ◦ ● ◦└̅┘◦│
_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jnosql-dev


--
Otávio Gonçalves de Santana
_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jnosql-dev
_______________________________________________
jnosql-dev mailing list
jnosql-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jnosql-dev


--
Otávio Gonçalves de Santana

Back to the top