You can specify what xPDOCache instance your cache items are stored in. If you take a look at the
getCache Extra, you can see that it, by default, stores it's cache items in the resource cache partition, but you can specify a cacheKey to target another existing, or even custom partition to store your items.
Consider if you wanted to cache the output of a Snippet longer than the Resource cache; you can target a custom cache partition that is not cleared by the normal cache refresh actions in MODX, and create a plugin attached specifically to events you want to trigger the partition to be flushed. I'm working on a blog post covering this topic to bring more attention to the flexible caching capabilities that are already at the disposal of MODX site developers.