[infinispan-dev] Multi tenancy support for Infinispan

[Radim Vansa]

As for the questions:
* Is SSL required for SNI? I can imagine that multi-tenancy would make 
sense even in situations when the connection does not need to be 
encrypted. Moreover, if we plan to eventually have HR clients with async 
API (and using async I/O), SSL is even more PITA. Btw., do we have any 
numbers how much SSL affects perf? (that's a question for QA, though)

* I don't think that dynamic switching of tenants would make sense, 
since that would require to invalidate all RemoteCache instances, near 
caches, connection pools, everything. So it's the same as starting from 
scratch.

R.





On 04/29/2016 05:29 PM, Sebastian Laskawiec wrote:
> Dear Community,
>
> Please have a look at the design of Multi tenancy support for 
> Infinispan [1]. I would be more than happy to get some feedback from you.
>
> Highlights:
>
>   * The implementation will be based on a Router (which will be built
>     based on Netty)
>   * Multiple Hot Rod and REST servers will be attached to the router
>     which in turn will be attached to the endpoint
>   * The router will operate on a binary protocol when using Hot Rod
>     clients and path-based routing when using REST
>   * Memcached will be out of scope
>   * The router will support SSL+SNI
>
> Thanks
> Sebastian
>
> [1] 
> https://github.com/infinispan/infinispan/wiki/Multi-tenancy-for-Hotrod-Server
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev


-- 
Radim Vansa <rvansa at redhat.com>
JBoss Performance Team