You don't particularly need distributed transactions if you design it right.
Generally try avoid them if you can. They have massive performance overheads.
The problem is that more often than not, you don't know the requirements beforehand.
I'm trying to come up with examples of transactions we have that span multiple services but can't come up with any. We do group tightly related functionality in the same service if we can. So if they need to be updated strictly transactionally they can usually be in the same DB-transaction.