[infinispan-dev] WildFly NoSQL client integration and Infinispan remote/JDG as a NoSQL client...

[Sanne Grinovero]

Hi Scott,

I don't think that having a default "testdb" would be useful if it
assumes that the user started an instance of Infinispan Server on a
"testhostmachine": very likely end users would want to at least change
the hostname; one might as well add the whole section at that point.

It could be more interesting if the user could lookup - eg via JNDI or
some connection URL - a reference to a client which is exposing the
same API be it a remote or a local CacheManager instance; in this case
you could have a local CacheManager instance started by default within
WildFly and have applications consume this.

But is it really useful for people to have a default, predefined testdb?

I wonder if it shouldn't rather be very easy for an application to
define what it needs, e.g. I'd allow applications to include a
"META-INF/caches.xml" to list the Caches needed by the application,
have WildFly create (and manage) these and provide a way for the
application to lookup the client, or have the client injected.

Thanks,
Sanne


On 12 May 2016 at 16:23, Scott Marlow <smarlow at redhat.com> wrote:
> Hi,
>
> Could you bring answers to the discussion [1] about using Infinispan as
> a remote NoSQL store in WildFly.
>
> Perhaps the WildFly standalone.xml subsystem configuration might define
> a "testdb" profile that any application deployment can use to remotely
> access the remote Infinispan server running on "testhostmachine" via
> configuration:
>
> "
> <subsystem xmlns="urn:jboss:domain:infinispan-nosql:1.0">
>   <infinispan name="default" id="dbtestprofile"
> jndi-name="java:jboss/infinispan/test" database="testdb">
>   <host name="default" outbound-socket-binding-ref="testhost"/>
>   </infinispan>
> </subsystem>
>
> <socket-binding-group name="standard-sockets" default-interface="public"
> port-offset="${jboss.socket.binding.port-offset:0}">
>   <outbound-socket-binding name="testhost">
>    <remote-destination host="testhostmachine" port="11234"/>
>   </outbound-socket-binding>
> </socket-binding-group>
> "
>
> Does this match at all with how you thought a WildFly application server
> might use a remote Infinispan server?
>
> Are there any concerns about marshalling, since the remote server
> (testhostmachine) may be a WildFly application server that doesn't have
> the same application deployments?
>
> Mostly, I'd like to discuss the above on [1] but here is fine also (we
> can link to this mailing list from [1], if we talk here).
>
> Scott
>
> [1] http://lists.jboss.org/pipermail/wildfly-dev/2016-May/004966.html
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev