how do u manage eventual consistency in distributed systems

we've been building out a new microservices architecture and are hitting the classic eventual consistency challenge. when services communicate asynchronously, how do you ensure that data eventually becomes consistent across all relevant services without resorting to complex distributed transactions? what patterns or tools have you found most effective for managing this, especially when dealing with failures or network partitions