How do you handle cache invalidation when data changes a lot?

hey everyone im wrestling with how to best invalidate cache entries when the underlying data changes frequently, we have a service where user-generated content can be updated multiple times an hour, were using redis for caching, but simply expiring entries after a set time feels too inefficient, leading to stale data or too many cache misses, what are your go-to strategies for handling cache invalidation in high-update scenarios, are there patterns beyond simple ttls or explicit deletion that youve found effective