As per my comments on rice-82:
I'm thinking that the name of this service might be a bit too general. I would think with something called a "CacheService" I would be able to put objects into the cache as well, which is something I really don't think we need on this service interface. Some ideas:
I would hesitate to put anything like "flush" in the name of this service. That's the only function it currently has, but I could see it being expanded in the future to support retrieving and assembling information from remote caches.