We're working on a huge caching implementation, and I'm trying to
figure out whether we should have one monstrous cache for the
application, or several smaller ones, specific to a subset of objects.
So for example, here's a subset of keys in our one current large
So we may have a cache with 10,000 such items in it. Would i be better
off setting up two caches in this case? One for Inventory, and one for
Accounts? Then I would just use the ID as the objectKey, and either
touch the Inventory or Accounts cache as appropriate. Is there a
performance consideration to using one over the other?