Have you had experience using transactions in microservice architecture?

In microservices architecture, the use of traditional ACID transactions is challenging due to the distributed nature of components. Instead, patterns such as:

• Sagas — a sequence of local transactions with compensating actions in case of errors.
• Idempotency — performing operations multiple times without changing the result.
• Eventual consistency — data consistency is achieved over time.

For example, when placing an order, one microservice reserves the product, another deducts money, and if one operation fails, compensating transactions are triggered to rollback changes.