How to organize the work of transactions in a microservice architecture?

Question

Highload

When developing an application with a microservice architecture, I encountered the problem of transactional data. At the moment there is an application that communicates with a number of microservices. It is necessary to update the data in one transaction in different microservices, while maintaining the integrity of the data. If one of the microservices could not process the request for some reason, the transaction should be rolled back. Tell me how to solve this problem on .net

Answer 1

Theoretical aspect: https://en.wikipedia.org/wiki/Two-phase_commit_protocol
Implementation: https://msdn.microsoft.com/en-us/library/system.tr... , well, or your bike (based on HTTP or message queuing).