What is the appropriate data expiration / eviction scheme for the following scenario

Question

We currently have an expiration scheme through which data entries in cache-A get expired after the cache hits a certain size. The LRU entries are expired after the max threshold is reached. But the issue is that certain entries in the cache are rendered meaningless without the other entries. There is a virtual grouping of entries in this cache.
Is there an expiration scheme that can be defined through which a group of entries can be deleted in one shot, and how can this policy be enforced.
The other way i would percieve this to work is to separate the currently virtually grouped entries into their own individual caches. This seems the logical thing to do, except for the issue being that we would still like to keep all these caches in the same service, and have an eviction policy defined at the service level instead of at the cache level.
Is it possible to define an eviction policy at the service level, for example to satisfy the below scenario.
Service-A has 10 caches in it [cache-1, cache-2, ....., cache-10]. And there is a limit of 10GB defined on the service. So, if the total utilization of all the caches in Service-A reaches 10GB, an entire cache from amongst [cache-1, cache-2, ....., cache-10] will need to be cleared and the memory be made available. Which one of the caches to be cleared will depend on which cache satisfies the LRU condition. So, maybe the entire cache-5 should be deleted if the entries in this cache was the oldest used.
Please let me know if the above scenario can be implemented.
Thanks
Sumax

Answer 1

Ricardo Pedro Rodrigues Ferrão wrote:
> Hi Eugene,
>
> I’ll try to explain it better.
>
> For example the business unit A is “portable pc” and I have this business unit in both companies and what I want in management consolidation is to consolidate data by the business unit “portable pc” joining data from both companies.
>
> Thanks.
Ricardo,
I had similar business scenario in my earlier project and the expectations were almost same.
I created one consolidation area (legal consolidation) under one single data basis and assigned business area as sub-assignment. All the consolidation functions are executed by the business users based on legal cons requirements purpose, while the reports can be generated for both legal and management consolidation.
In management consolidation reporting, your expectations can be met easily. The header will be business area, while line item data will be companies wise (if you would like the data to display that way).
For more information, you can check the threads created by me.