cache invalidation for user-generated content, any battle-tested strategies

hey everyone, im wrestling with cache invalidation for content that users themselves create and modify. think user profiles, posts, comments, and so on. standard ttl-based invalidation feels a bit blunt when content can change unexpectedly. how do you guys handle this. are there specific patterns or tools youve found effective beyond just setting a short ttl. im curious about your war stories here