ThornTail v4 NoSQL integration ideas...

[Scott Marlow]

I just released wildfly-nosql 1.0.0.Final, which will soon come into the v2 branch (pull#1065 + THORN-2117).  For the v4 branch effort, I'd like to understand what might be most needed (by users) in the NoSQL area of integration.  I have some ideas in mind, but really, I'd rather hear from all of you first, what you think the big problems to solve, are for v4 + NoSQL.

Later, I will also do some planning/coding/testing for wildfly-nosql 2.0, for ThornTail v2.  One of the v2 ideas, is to simplify the native NoSQL driver interaction, to not use MethodHandle anymore.  The idea here, as suggested by the Hibernate OGM team, is to use an integration api for integrating with different versions of each NoSQL backend.  I'll return to working on this, after spending some time on v4 NoSQL integration.

Thanks for your ideas!

Scott

[Werner Keil]

I know there's Hibernate OGM, but for a vendor neutral approach that aims to join the Jakarta EE platform as soon as that has been fully established, what about Eclipse JNoSQL?

Werner

[Sergey Beryozkin]

Might be useful to have an OOB log handler that the users will use to save the various v4 log events in the NoSql databases.

Sergey

--
You received this message because you are subscribed to the Google Groups "Thorntail" group.
To unsubscribe from this group and stop receiving emails from it, send an email to thorntail+unsubscribe@googlegroups.com.
To post to this group, send email to thor...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/thorntail/a5ba4832-f65a-4492-9952-6896f6c075fe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Scott Marlow]

On Friday, August 3, 2018 at 9:38:15 AM UTC-4, Werner Keil wrote:

I know there's Hibernate OGM, but for a vendor neutral approach that aims to join the Jakarta EE platform as soon as that has been fully established, what about Eclipse JNoSQL?

OGM is definitely on the list! :)

I also think it will be great to have a common call level interface approach for NoSQL applications and agree, we should also integrate with JNoSQL (as well as native NoSQL APIs). 

Other than providing some samples of using JNoSQL with ThornTail V4, do you have additional JNoSQL integration ideas to share?  For example, are there additional CDI integration classes, to work with JNoSQL, that should come with ThornTail?  What should the additional CDI integration classes do, that isn't already done by the CDI integration classes in JNoSQL? 

Perhaps we could also leverage a platform level interface, for hooking into connection management and other internal aspects of the NoSQL native clients or of the JNoSQL layering, for things that we might want to show up in a management console.

Scott

 

Werner

[Scott Marlow]

On Tuesday, August 7, 2018 at 7:24:58 AM UTC-4, Sergey Beryozkin wrote:

Might be useful to have an OOB log handler that the users will use to save the various v4 log events in the NoSql databases.

Would this log messages to the NoSql databases in the background, via an async logger?  Or does an OOB log handler, operate differently than that?

Scott

Sergey

[Sergey Beryozkin]

Hi

I meant that may be shipping the ready to be used handler with Thorntail v4 can be handy, so that users do not have to write it themselves whenever they need it, given that v4 will have the NoSql 'infrastructure' around. I'm not sure about the actual implementation strategy though :-). Logging to the NoSql asynchronously seems like a nice idea...

Sergey 

--
You received this message because you are subscribed to the Google Groups "Thorntail" group.
To unsubscribe from this group and stop receiving emails from it, send an email to thorntail+unsubscribe@googlegroups.com.
To post to this group, send email to thor...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/thorntail/8b5da9b2-212d-4fca-bfeb-d9682fe8e17b%40googlegroups.com.