what's my fave way to handle eventual consistency in distributed systems

i've been wrestling with eventual consistency lately, especially when dealing with microservices that don't need to be strictly synchronous. things like read-your-writes and write-your-reads have been on my mind. what are your go-to patterns or strategies for ensuring data eventually aligns without resorting to heavy two-phase commits? i'm curious about practical examples and trade-offs you've encountered.