When should you aggressively cache noncritical read data

hey folks, i've been thinking about scaling read-heavy services. we have a lot of data that doesn't change often and isn't super critical if it's a minute or two stale. i'm considering implementing aggressive caching strategies for this data, maybe even with client-side caching or very long TTLs on shared caches. has anyone had success or horror stories with this kind of approach? what are the pitfalls to watch out for, beyond the usual cache invalidation headaches. looking for real-world experiences and thoughts on the trade-offs