Saga Pattern or Two-Phase Commit for Distributed Transactions?

hey all, i've been wrestling with distributed transactions in a microservices context lately. my team is considering the saga pattern as an alternative to traditional two-phase commit (2pc) to avoid tight coupling and potential blocking issues. we're looking at scenarios where we need to maintain data consistency across multiple services. what are your experiences with implementing sagas? what were the biggest gotchas or benefits you found compared to 2pc? are there specific types of operations where one clearly outperforms the other?