Apparatuses, methods, and computer program products for application component workflows based on a distributed ledger
Methods, apparatuses, or computer program products provide application component workflows based on a distributed ledger. At least a first workflow vector data structure associated with a first workflow action within an application component and a second workflow vector data structure associated with a second workflow action within the application component can be identified. In response to the first workflow vector data structure and the second workflow vector data structure satisfying workflow action criteria, a candidate transaction associated with the first workflow vector data structure and the second workflow vector data structure can be determined for a distributed ledger. Additionally, a candidate transaction data structure for the candidate transaction is generated in accordance with one or more candidate transaction attributes and execution of a smart contract of the distributed ledger is caused to add the candidate transaction data structure to the distributed ledger and render at least the first workflow action and the second workflow action immutable.
1 . An apparatus comprising one or more processors and one or more storage devices storing instructions that are operable, when executed by the one or more processors, to cause the one or more processors to:
generate smart contract rules associated with a distributed ledger based at least in part on one or more latency requirements for a workflow event associated with one or more changes with respect to one or more workflows within an application component of an application framework;
generate a smart contract of the distributed ledger based at least in part on the smart contract rules, wherein execution of the smart contract causes one or more candidate transaction data structure to be added to the distributed ledger in response to the smart contract rules being satisfied;
monitor a workflow event stream associated with one or more workflow events associated with the application component of the application framework, wherein the one or more workflow events are triggered by at least one user computing device interacting with the application component of the application framework via a network;
identify, based at least on the workflow event stream, one or more changes with respect to computer functionality of the application component during execution of the application component via the application framework, wherein the workflow event stream comprises at least a first workflow vector data structure associated with a first workflow action within the application component and a second workflow vector data structure associated with a second workflow action within the application component, wherein the first workflow action and the second workflow action respectively correspond to at least a portion of a workflow of the application component that is associated with the one or more changes, and wherein the first workflow action transitions the workflow to a first workflow status, and the second workflow action transitions the workflow to a second workflow status;
based at least in part on the one or more latency requirements, store the first workflow vector data structure and the second workflow vector data structure in a Level 1 cache memory;
in response to the first workflow vector data structure and the second workflow vector data structure satisfying workflow action criteria for one or more workflow attributes of a defined transition within the workflow, determine, for a distributed ledger, a candidate transaction associated with the first workflow vector data structure and the second workflow vector data structure;
generate a candidate transaction data structure for the candidate transaction in accordance with one or more candidate transaction attributes of the candidate transaction; and
cause execution of the smart contract of the distributed ledger to add the candidate transaction data structure to the distributed ledger in accordance with a distributed ledger consensus protocol based on a comparison between the one or more candidate transaction attributes and the smart contract rules for the smart contract, wherein adding the candidate transaction data structure to the distributed ledger prevents data associated with at least the first workflow action and the second workflow action from being altered.
2 . The apparatus of claim 1 , wherein the first workflow action and the second workflow action are associated with the workflow event.
3 . The apparatus of claim 1 , wherein the one or more storage devices store instructions that are operable, when executed by the one or more processors, to further cause the one or more processors to:
determine whether the first workflow vector data structure and the second workflow vector data structure satisfy a defined status for the workflow.
4 . The apparatus of claim 1 , wherein the one or more storage devices store instructions that are operable, when executed by the one or more processors, to further cause the one or more processors to:
determine whether the first workflow vector data structure and the second workflow vector data structure satisfy a defined transition for the workflow.
5 . The apparatus of claim 1 , wherein the one or more storage devices store instructions that are operable, when executed by the one or more processors, to further cause the one or more processors to:
generate the candidate transaction data structure for the candidate transaction based on metadata included in the first workflow vector data structure.
6 . The apparatus of claim 1 , wherein the one or more storage devices store instructions that are operable, when executed by the one or more processors, to further cause the one or more processors to:
generate the candidate transaction data structure for the candidate transaction based on metadata included in the second workflow vector data structure.
7 . The apparatus of claim 1 , wherein the one or more storage devices store instructions that are operable, when executed by the one or more processors, to further cause the one or more processors to:
generate the candidate transaction data structure for the candidate transaction based on first metadata included in the first workflow vector data structure and second metadata included in the second workflow vector data structure.
8 . The apparatus of claim 1 , wherein the smart contract rules for the smart contract are configured by one or more user identifiers authorized with respect to the application component.
9 . The apparatus of claim 1 , wherein the smart contract rules for the smart contract are predetermined smart contract rules associated with an application framework.
10 . The apparatus of claim 1 , wherein the one or more storage devices store instructions that are operable, when executed by the one or more processors, to further cause the one or more processors to:
configure one or more smart contract rules of the smart contract rules based on one or more defined workflow actions for the workflow.
11 . The apparatus of claim 1 , wherein the Level 1 cache memory is integrated into a microprocessor.
12 . The apparatus of claim 1 , wherein the one or more storage devices store instructions that are operable, when executed by the one or more processors, to further cause the one or more processors to:
configure a portion of the smart contract rules for the smart contract based on an interface element of a user interface.
13 . A computer-implemented method, comprising:
generating smart contract rules associated with a distributed ledger based at least in part on one or more latency requirements for a workflow event associated with one or more changes with respect to one or more workflows within an application component of an application framework;
generating a smart contract of the distributed ledger based at least in part on the smart contract rules, wherein execution of the smart contract causes one or more candidate transaction data structure to be added to the distributed ledger in response to the smart contract rules being satisfied;
monitoring a workflow event stream associated with one or more workflow events associated with the application component of the application framework, wherein the one or more workflow events are triggered by at least one user computing device interacting with the application component of the application framework via a network;
identifying, based at least on the workflow event stream, one or more changes with respect to computer functionality of the application component during execution of the application component via the application framework, wherein the workflow event stream comprises at least a first workflow vector data structure associated with a first workflow action within the application component and a second workflow vector data structure associated with a second workflow action within the application component, wherein the first workflow action and the second workflow action respectively correspond to at least a portion of a workflow of the application component that is associated with the one or more changes, and wherein the first workflow action transitions the workflow to a first workflow status, and the second workflow action transitions the workflow to a second workflow status;
based at least in part on the one or more latency requirements, storing the first workflow vector data structure and the second workflow vector data structure in a Level 1 cache memory;
in response to the first workflow vector data structure and the second workflow vector data structure satisfying workflow action criteria for one or more workflow attributes of a defined transition within the workflow, determining, for a distributed ledger, a candidate transaction associated with the first workflow vector data structure and the second workflow vector data structure;
generating a candidate transaction data structure for the candidate transaction in accordance with one or more candidate transaction attributes of the candidate transaction; and
causing execution of the smart contract of the distributed ledger to add the candidate transaction data structure to the distributed ledger in accordance with a distributed ledger consensus protocol based on a comparison between the one or more candidate transaction attributes and the smart contract rules for the smart contract, wherein adding the candidate transaction data structure to the distributed ledger prevents data associated with at least the first workflow action and the second workflow action from being altered.
14 . The computer-implemented method of claim 13 , wherein the first workflow action and the second workflow action are associated with the workflow event.
15 . The computer-implemented method of claim 13 , further comprising:
determining whether the first workflow vector data structure and the second workflow vector data structure satisfy a defined status for the workflow.
16 . The computer-implemented method of claim 13 , further comprising:
determining whether the first workflow vector data structure and the second workflow vector data structure satisfy a defined transition for the workflow.
17 . The computer-implemented method of claim 13 , further comprising:
generating the candidate transaction data structure for the candidate transaction based on metadata included in the first workflow vector data structure.
18 . The computer-implemented method of claim 13 , further comprising:
generating the candidate transaction data structure for the candidate transaction based on metadata included in the second workflow vector data structure.
19 . The computer-implemented method of claim 13 , wherein generating the candidate transaction data structure comprises generating the candidate transaction data structure for the candidate transaction based on first metadata included in the first workflow vector data structure and second metadata included in the second workflow vector data structure.
20 . The computer-implemented method of claim 13 , wherein the smart contract rules for the smart contract are configured by one or more user identifiers authorized with respect to the application component.
21 . The computer-implemented method of claim 13 , wherein the smart contract rules for the smart contract are predetermined smart contract rules associated with an application framework.
22 . The computer-implemented method of claim 13 , further comprising:
configuring one or more smart contract rules of the smart contract rules based on one or more defined workflow actions for the workflow.
23 . The computer-implemented method of claim 13 , wherein the Level 1 cache memory is integrated into a microprocessor.
24 . The computer-implemented method of claim 13 , further comprising:
configuring a portion of the smart contract rules for the smart contract based on an interface element of a user interface.
25 . A non-transitory computer readable medium comprising instructions that, when executed by one or more computers, cause the one or more computers to:
generate smart contract rules associated with a distributed ledger based at least in part on one or more latency requirements for a workflow event associated with one or more changes with respect to one or more workflows within an application component of an application framework;
generate a smart contract of the distributed ledger based at least in part on the smart contract rules, wherein execution of the smart contract causes one or more candidate transaction data structure to be added to the distributed ledger in response to the smart contract rules being satisfied;
monitor a workflow event stream associated with one or more workflow events associated with the application component of the application framework, wherein the one or more workflow events are triggered by at least one user computing device interacting with the application component of the application framework via a network;
identify, based at least on the workflow event stream, one or more changes with respect to computer functionality of the application component during execution of the application component via the application framework, wherein the workflow event stream comprises at least a first workflow vector data structure associated with a first workflow action within the application component and a second workflow vector data structure associated with a second workflow action within the application component, wherein the first workflow action and the second workflow action respectively correspond to at least a portion of a workflow of the application component that is associated with the one or more changes, and wherein the first workflow action transitions the workflow to a first workflow status, and the second workflow action transitions the workflow to a second workflow status;
based at least in part on the one or more latency requirements, store the first workflow vector data structure and the second workflow vector data structure in a Level 1 cache memory;
in response to the first workflow vector data structure and the second workflow vector data structure satisfying workflow action criteria for one or more workflow attributes of a defined transition within the workflow, determine, for a distributed ledger, a candidate transaction associated with the first workflow vector data structure and the second workflow vector data structure;
generate a candidate transaction data structure for the candidate transaction in accordance with one or more candidate transaction attributes of the candidate transaction; and
cause execution of the smart contract of the distributed ledger to add the candidate transaction data structure to the distributed ledger in accordance with a distributed ledger consensus protocol based on a comparison between the one or more candidate transaction attributes and the smart contract rules for the smart contract, wherein adding the candidate transaction data structure to the distributed ledger prevents data associated with at least the first workflow action and the second workflow action from being altered.
26 . The non-transitory computer readable medium of claim 25 , wherein the first workflow action and the second workflow action are associated with the workflow event.
27 . The non-transitory computer readable medium of claim 25 , further comprising instructions that, when executed by the one or more computers, cause the one or more computers to:
determine whether the first workflow vector data structure and the second workflow vector data structure satisfy a defined status for the workflow.
28 . The non-transitory computer readable medium of claim 25 , further comprising instructions that, when executed by the one or more computers, cause the one or more computers to:
determine whether the first workflow vector data structure and the second workflow vector data structure satisfy a defined transition for the workflow.
29 . The non-transitory computer readable medium of claim 25 , further comprising instructions that, when executed by the one or more computers, cause the one or more computers to:
generate the candidate transaction data structure for the candidate transaction based on metadata included in the first workflow vector data structure.
30 . The non-transitory computer readable medium of claim 25 , further comprising instructions that, when executed by the one or more computers, cause the one or more computers to:
generate the candidate transaction data structure for the candidate transaction based on metadata included in the second workflow vector data structure.
31 . The non-transitory computer readable medium of claim 25 , further comprising instructions that, when executed by the one or more computers, cause the one or more computers to:
generate the candidate transaction data structure for the candidate transaction based on first metadata included in the first workflow vector data structure and second metadata included in the second workflow vector data structure.
32 . The non-transitory computer readable medium of claim 25 , wherein the smart contract rules for the smart contract are configured by one or more user identifiers authorized with respect to the application component.
33 . The non-transitory computer readable medium of claim 25 , wherein the smart contract rules for the smart contract are predetermined smart contract rules associated with an application framework.
34 . The non-transitory computer readable medium of claim 25 , further comprising instructions that, when executed by the one or more computers, cause the one or more computers to:
configure one or more smart contract rules of the smart contract rules based on one or more defined workflow actions for the workflow.
35 . The non-transitory computer readable medium of claim 25 , wherein the Level 1 cache memory is integrated into a microprocessor.
36 . The non-transitory computer readable medium of claim 25 , further comprising instructions that, when executed by the one or more computers, cause the one or more computers to:
configure a portion of the smart contract rules for the smart contract based on an interface element of a user interface.