The Caching API currently is quite low-level. Tagging is useful to flush specific parts, but the tagging and flushing itself must still completly be implemented manually.
I think there are a few usecases that could be simplefied through some api love:
- cache-entry for specific conditional arguments
- cache-entry conditionally based on current user roles
- cache-entry based on one or all entities of a specific type, maybe even a specific property
- cache-entry based on directory/path changes
I could imagine to do this with a 'cacheEntry' API layer above the current Caching API: