Consider leveraging `mailgun/groupcache`

[tmc]

As you may be aware the folks at mailgun have forked groupcache: mailgun/groupcache. This fork includes a few features that seem relevant here, namely, TTL and Removal support.

I'm interested in using this package but not having a very clean path for on-demand invalidation is a big of a snag.

[ancientlore]

I will consider this but want to look at it a bit. As I split out this library last night, I was thinking of how it would be interesting to make the cache more pluggable - because there are hundreds of forks of groupcache, all somewhat similar. If that can be decoupled, it would solve your use case and others. But I need to consider if that is something that can be reasonably implemented.

[ancientlore]

One challenge with mailgun/groupcache is that it adds a logrus dependency, which for my purposes is bloat. It would be an easier decision to use it if they removed that, or replaced it with only the structured logging package (if that is adopted into the standard library).