Feature #54652
closed
Caching Framework should allow multiple backends
0%
Description
Backends would be queried in order. For example you could have a transient backend for queries during a request and a db-backend. Or a small but fast memcache-backend and a DB-backend behind that.
It would be possible to implement a "ChainedBackend" which would then handle multiple backends itself.
(How would writes be handled? Write to all backends?)
Updated by
Updated by Christian Kuhn about 9 years ago
- Status changed from New to Rejected
I think this i a bad idea. First and second level caching strategies should be implemented in the calling code and not hidden in the relatively straight cache implementation that would be heavily bloated implementing such an approach. I once had the idea to have separated tags and data backends to solve some systematic issues in this area for not suitable backends, but this is also more a problem than a solution.
I'll close this issue as rejected for now, since I don't think the architecture should be extended this way blindly.