Distributed transaction handling
Distributed transaction facilitates the execution of multiple operations as a single unit of work. In a distributed transaction, a command is an operation that performs a state change and causes an event to occur. These events might alert the next phase or the entire system of the transaction's success or failure. If they are successful, they can cause another command to be performed, which can then cause an event, and this will continue until all transactions are completed or rolled back, depending on whether the transaction is successful or not. Let's explore the important aspects to consider while evaluating this factor, as follows:
- How many distributed transactions exist in the system?
- What is your approach to handling distributed transactions—is it using an orchestrator or choreography pattern?
- How many transactions span over multiple services?
- Are you using a long-chain operation when a transaction spans...
