2) Segmenting shared cache. Caching of data in the process-scoped,Completely agree. Web scale applications are architected to use
shared cache needs to be segmented by each tenant since we are
talking about the same process. Actually this is a concern anyway in
implementing PaaS style multi-tenancy depending on how the cache
provider is deployed, so not sure this is that big of a deal.
Of course, as pointed out before, even if this is deemed outside the
scope of JPA 2.1, nothing stops the individual providers from
implementing this support.
systems like Memcached to keep the cached data partitioned/segmented.
In this context, JPA vendors could think of integrating their shared
caches with systems like Memcached or JCache based implementations
with a few partitioning strategies.
[jsr338-experts] Re: support for multitenancy