Management of sequenced execution of service tasks in a multi-service system
A method and system for optimizing the interaction and execution of multiple service tasks associated with a logical transaction. The multiple components or “legs” of the transaction consisting of tasks executable by a computing service or software as a service (SAAS) endpoint are identified. The system determines a strategy type or belief level associated with each of the service tasks included in a transaction. The belief level may be categorized as either “optimistic” or “pessimistic” based on one or more performance parameters (e.g., a probability of failure of a service and an expense associated with a failure of the service) derived from historical data associated with a particular transaction or service task. A sequence of execution for the multiple service tasks associated with the transaction is determined based at least in part on the belief level associated with each of the multiple service tasks. In one embodiment, one or more unordered service tasks classified as pessimistic are performed before one or more unordered service tasks classified as optimistic.
1. A method to optimize execution of a plurality of service tasks associated with a transaction, the method comprising:
identifying the plurality of service tasks associated with the transaction requested by a customer system;
identifying:
a first set of ordered service tasks of the plurality of service tasks that have a dependent relationship with one or more other service tasks of the plurality of service tasks, and
a second set of unordered service tasks of the plurality of service tasks that are independent from other service tasks of the plurality of service tasks;
determining a sequence of serial execution of the first set of ordered service tasks;
executing the first set of ordered service tasks in the sequence;
determining a belief score for each of the second set of unordered service tasks, wherein the belief score represents at least one of a probability of failure of a service task or an expense associated with the failure of the service task;
identifying a first subset of the second set of unordered service tasks having a respective belief score greater than or equal to a threshold value;
identifying a second subset of the second set of unordered service tasks having a respective belief score less than the threshold value;
executing, in descending order of the respective belief score, the first subset of the second set of unordered service tasks; and
in response to completion of the execution of the first subset of the second set of unordered service tasks, executing, in parallel, the second subset of the second set of unordered service tasks.
2. The method of claim 1 , wherein execution of the first set of ordered service tasks, the first subset of the unordered service tasks, and the second subset of unordered service tasks results in execution of the transaction.
3. The method of claim 1 , further comprising identifying an error associated with a first service task of the plurality of service tasks.
4. The method of claim 3 , further comprising:
determining a type of the error associated with the first service task; and
determining a first belief score associated the first service task.
5. The method of claim 4 , further comprising determining a retry period of time associated with the first service task based at least in part on the type of error and the first belief score.
6. A system to optimize execution of a plurality of service tasks associated with a transaction, the system comprising:
a processing device; and
a memory to store computer-executable instructions that, if executed, cause the processing device to:
identify the plurality of service tasks associated with the transaction requested by a customer system;
identify:
a first set of ordered service tasks of the plurality of service tasks that have a dependent relationship with one or more other service tasks of the plurality of service tasks, and
a second set of unordered service tasks of the plurality of service tasks that are independent from other service tasks of the plurality of service tasks;
determine a sequence of serial execution of the first set of ordered service tasks;
execute the first set of ordered service tasks in the sequence;
determine a belief score for each of the second set of unordered service tasks wherein the belief score represents at least one of a probability of failure of a service task or an expense associated with the failure of the service task;
identify a first subset of the second set of unordered service tasks having a respective belief score greater than or equal to a threshold value;
identify a second subset of the second set of unordered service tasks having a respective belief score less than the threshold value;
execute, in descending order of the respective belief score, the first subset of the second set of unordered service tasks; and
in response to completion of the execution of the first subset of the second set of unordered service tasks, execute, in parallel, the second subset of the second set of unordered service tasks.
7. The system of claim 6 , wherein execution of the first set of ordered service tasks, the first subset of the unordered service tasks, and the second subset of unordered service tasks results in execution of the transaction.
8. The system of claim 6 , the processing device to identify an error associated with a first service task of the plurality of service tasks.
9. The system of claim 8 , the processing device to:
determine a type of the error associated with the first service task; and
determine a first belief score associated the first service task.
10. The system of claim 9 , the processing device to:
determining a retry period of time associated with the first service task based at least in part on the type of error and the first belief score.
11. A non-transitory computer-readable storage device storing computer-executable instructions to optimize execution of a plurality of service tasks associated with a transaction, the instructions, if executed by a processing device, cause the processing device to:
identify the plurality of service tasks associated with the transaction requested by a customer system;
identify:
a first set of ordered service tasks of the plurality of service tasks that have a dependent relationship with one or more other service tasks of the plurality of service tasks, and
a second set of unordered service tasks of the plurality of service tasks that are independent from other service tasks of the plurality of service tasks;
determine a sequence of serial execution of the first set of ordered service tasks;
execute the first set of ordered service tasks in the sequence;
determine a belief score for each of the second set of unordered service tasks wherein the belief score represents at least one of a probability of failure of a service task or an expense associated with the failure of the service task;
identify a first subset of the second set of unordered service tasks having a respective belief score greater than or equal to a threshold value;
identify a second subset of the second set of unordered service tasks having a respective belief score less than the threshold value;
execute, in descending order of the respective belief score, the first subset of the second set of unordered service tasks; and
in response to completion of the execution of the first subset of the second set of unordered service tasks, execute, in parallel, the second subset of the second set of unordered service tasks.
12. The non-transitory computer-readable storage device of claim 11 , wherein execution of the first set of ordered service tasks, the first subset of the unordered service tasks, and the second subset of unordered service tasks results in execution of the transaction.
13. The non-transitory computer-readable storage device of claim 11 , the processing device to identify an error associated with a first service task of the plurality of service tasks.
14. The non-transitory computer-readable storage device of claim 13 , the processing device to:
determine a type of the error associated with the first service task;
determine a first belief score associated the first service task; and
determine a retry period of time associated with the first service task based at least in part on the type of error and the first belief score.