how do you handle cache consistency across multiple microservices tho

We're building out a new set of microservices, and we're really counting on caching to speed things up and take some pressure off the database. The tricky part is that several services might need to read and change the same cached information. This makes me worried about keeping the cache consistent. For instance, if Service A updates a user's profile and then clears the cache for it, how do we make sure Service B, which also needs that profile data, doesn't end up showing old, outdated info? What approaches or designs have worked well for you when dealing with cache consistency in a distributed microservices setup? Any particular tools or libraries you'd suggest?