The following use cases currently involve redundant cache operations when near cache is disabled.

• ATTRIBUTE granularity sessions require duplicate remote cache lookups for existing sessions

Additionally, because near cache invalidation also invalidates itself - there are additional cases where enabling near caching requires redundant cache operations:

• ATTRIBUTE granularity attribute reads following a write require an additional remote lookup

Other redundancies (independent of near caching) include:

• Updates to the session index used by ATTRIBUTE granularity require N operations, rather than a single operation.
• Updates to ATTRIBUTE granularity session attributes require N operations, rather than using bulk operations, e.g. putAll