Direct launch for asynchronous actions
Techniques are disclosed herein for a direct launch for asynchronous actions. An example method can include receiving, by a device, a first workflow request, wherein the device comprises a first launcher in operable communication with a second launcher via a shared queue, and wherein a first duplicate of the first workflow request is stored in the shared queue is to be retrieved by the second launcher upon an elapsing of a threshold time interval. The device can transmit the workflow request to an application for executing the first workflow request, wherein the transmission is prior to the threshold time elapsing. The device can determine whether the application initiated a workflow to process the workflow request. The device can update the first duplicate of the first workflow request stored at the shared queue based at least in part on the determination and prior to the threshold time interval elapsing.
1 . A method, comprising;
receiving, by a computing device, a first workflow request, the device comprising a first launcher in communication with a second launcher via a shared queue, and a first duplicate of the first workflow request being stored in the shared queue to be retrieved by the second launcher upon an elapsing of a threshold time interval;
transmitting, by the computing device, the first workflow request to an application for executing the first workflow request, the transmission being prior to the threshold time elapsing;
determining, by the computing device, whether the application initiated a workflow to process the first workflow request;
in accordance with determining that the application initiated the workflow process to process the first workflow request and prior to the threshold time interval elapsing, updating, by the computing device, the first duplicate of the first workflow request stored at the shared queue;
generating a second duplicate of the first workflow request;
receiving a second workflow request via an application programming interface (API);
compressing the second duplicate of the first workflow request and the second workflow request into a batch; and
updating a first duplicate of the second workflow request based at least in part on the compression.
2 . The method of claim 1 , wherein the method further comprises generating a third launcher, based at least in part on a real-time performance metric of the device, wherein the second workflow request is received via the third launcher.
3 . The method of claim 1 , wherein updating the first duplicate of the first workflow request comprising generating an instruction based at least in part on compression of the second workflow request and the second duplicate of the first workflow request.
4 . The method of claim 1 , wherein the threshold time interval is based at least in part on a projected latency between the first duplicate of the first workflow request being loaded onto the shared queue and the second launcher retrieving the first duplicate of the first workflow request from the shared queue.
5 . The method of claim 1 , wherein the first workflow request is received via an in-memory queue.
6 . The method of claim 1 , wherein updating the duplicate of the first workflow request comprises deleting the duplicate of the first workflow request.
7 . A device, comprising:
a processor; and
a computer-readable medium including instructions that, when executed by the processor, cause the processor to perform operations comprising:
receiving, by a computing device, a first workflow request, the device comprising a first launcher in communication with a second launcher via a shared queue, and a first duplicate of the first workflow request being stored in the shared queue to be retrieved by the second launcher upon an elapsing of a threshold time interval;
transmitting, by the computing device, the first workflow request to an application for executing the first workflow request, the transmission being prior to the threshold time elapsing;
determining, by the computing device, whether the application initiated a workflow to process the first workflow request;
in accordance with determining that the application initiated the workflow process to process the first workflow request and prior to the threshold time interval elapsing, updating, by the computing device, the first duplicate of the first workflow request stored at the shared queue;
generating a second duplicate of the first workflow request;
receiving a second workflow request via an application programming interface;
compressing the second duplicate of the first workflow request and the second workflow request into a batch; and
updating a first duplicate of the second workflow request based at least in part on the compression.
8 . The device of claim 7 , wherein the instructions that, when executed by the processor, cause the processor to perform operations comprising generating a third launcher, based at least in part on a real-time performance metric of the device, wherein the second workflow request is received via the third launcher.
9 . The device of claim 7 , wherein generating the instruction is further based at least in part on compression of the second workflow request and the second duplicate of the first workflow request.
10 . The device of claim 7 , wherein the threshold time interval is based at least in part on a projected latency between the first duplicate of the first workflow request being loaded onto the shared queue and the second launcher retrieving the first duplicate of the first workflow request from the shared queue.
11 . The device of claim 7 , wherein the first workflow request is received via an in-memory queue.
12 . The device of claim 7 , wherein updating the duplicate of the first workflow request comprises deleting the duplicate of the first workflow request.
13 . A non-transitory, computer-readable medium having stored thereon a sequence of instructions which, when executed, causes a processor to perform operations comprising:
receiving, by a computing device, a first workflow request, the device comprising a first launcher in communication with a second launcher via a shared queue, and a first duplicate of the first workflow request being stored in the shared queue to be retrieved by the second launcher upon an elapsing of a threshold time interval;
transmitting, by the computing device, the first workflow request to an application for executing the first workflow request, the transmission being prior to the threshold time elapsing;
determining, by the computing device, whether the application initiated a workflow to process the first workflow request; and
in accordance with determining that the application initiated the workflow process to process the first workflow request and prior to the threshold time interval elapsing, updating, by the computing device, the first duplicate of the first workflow request stored at the shared queue;
generating a second duplicate of the first workflow request;
receiving a second workflow request via an application programming interface;
compressing the second duplicate of the first workflow request and the second workflow request into a batch; and
updating a first duplicate of the second workflow request based at least in part on the compression.
14 . The non-transitory, computer-readable medium of claim 13 , wherein the instructions that, when executed by the processor, cause the processor to perform operations comprising generating a third launcher, based at least in part on a real-time performance metric of the device, wherein the second workflow request is received via the third launcher.
15 . The non-transitory, computer-readable medium of claim 13 , wherein generating the instruction is further based at least in part on compression of the second workflow request and the second duplicate of the first workflow request.
16 . The non-transitory, computer-readable medium of claim 13 , wherein the threshold time interval is based at least in part on a projected latency between the first duplicate of the first workflow request being loaded onto the shared queue and the second launcher retrieving the first duplicate of the first workflow request from the shared queue.
17 . The non-transitory, computer-readable medium of claim 13 , wherein the first workflow request is received via an in-memory queue.