microservices: how to handle distributed transactions? like, dont you hate it when that happens?

were moving towards a microservices architecture and facing the classic challenge of managing transactions that span multiple services. traditional two-phase commit (2PC) seems like overkill and introduces tight coupling. ive been reading about patterns like Saga, but im curious about real-world experiences. what approaches have you found effective for distributed transactions in microservices? are there specific scenarios where one pattern shines over others? lets discuss the trade-offs and practical considerations.