While participating in one of those issues, I've proposed a way to do field-based cache invalidation.
The path I’m specifying here is for /*, but you’ll want to update that to match the path for your use case.
When you sign in to comment, IBM will provide your email, first name and last name to DISQUS.
We have some pages that have 7 or 8 separately cached subcomponents that expire based on a range of criteria.
Our component cache names reflect the key objects (or object classes) and are used to identify what needs to be invalidated on certain updates.
When you want to expire the cache for that absolute url you increment its generation value (to two in this case).