Automatically executing stateless transactions with data dependency in test cases
US-2019065349-A1 · Feb 28, 2019 · US
US10733018B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10733018-B2 |
| Application number | US-201815965283-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 27, 2018 |
| Priority date | Apr 27, 2018 |
| Publication date | Aug 4, 2020 |
| Grant date | Aug 4, 2020 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods and systems for providing an external scheduler in a stateless application framework are presented. A first instance of a stateless application transmits a job request to a data processing engine, and submits a message to a messaging queue. The message indicates a task to be performed according to a delayed schedule. The first instance of the stateless application terminates after submitting the message. The messaging queue transmits the message to the stateless application framework according to the delayed schedule. Upon receiving the message, a second instance of the stateless application is instantiated. The second instance of the stateless application performs an action based on the message and terminates.
Opening claim text (preview).
What is claimed is: 1. A method comprising: obtaining, by a first instance of a stateless application executed on a computer system, a workflow associated with a user account, wherein the workflow indicates a first task and a second task, wherein the second task is associated with a delayed schedule; transmitting, by the first instance of the stateless application, a job request to a data processing engine based on the first task indicated in the workflow; submitting, by the first instance of the stateless application to a messaging module, a message addressed to the stateless application based on the workflow, wherein the message comprises a reference to the user account and the second task; in response to receiving the message from the messaging module, instantiating, by the computer system, a second instance of the stateless application; and performing, by the second instance of the stateless application, the second task based on the message. 2. The method of claim 1 , wherein the second task comprises a job status inquiry associated with the job request, and wherein the performing the second task comprises transmitting a job status inquiry request to the data processing engine. 3. The method of claim 1 , wherein the data processing engine is a first data processing engine, wherein the method further comprises receiving, from a second data processing engine, an indication of an event associated with the user account, and wherein the transmitting of the job request is responsive to receiving the indication. 4. The method of claim 3 , further comprising in response to receiving the indication, accessing, by the first instance of the stateless application, a context database to create a record for the event, wherein the record comprises state data indicating a context of the user account within a state machine configuration. 5. The method of claim 4 , wherein the second task comprises a state inquiry associated with the user account, wherein the performing the second task comprises: accessing, by the second instance of the stateless application, the context database to retrieve the state data from the record; and transmitting the state data to the second data processing engine. 6. The method of claim 4 , further comprising: in response to receiving a response from the first data processing engine, instantiating, by the computer system, a third instance of the stateless application; and accessing, by the third instance of the stateless application, the context database to update the context of the user account by inserting second context data to the record based on the response. 7. The method of claim 4 , wherein the message comprises a session identifier that identifies the user account, the event, and the state machine configuration. 8. The method of claim 7 , wherein the indication comprises an account identifier associated with the user account and an event identifier associated with the event, and wherein the method further comprises: selecting, from a plurality of state machine configurations, the state machine configuration corresponding to the event; and generating the session identifier based on the user identifier, the event identifier, and a configuration identifier associated with the state machine configuration. 9. The method of claim 1 , wherein the delayed schedule comprises a frequency. 10. The method of claim 1 , wherein the messaging module is external to the stateless application. 11. The method of claim 1 , further comprising terminating the first instance of the stateless application after submitting the message to the messaging module. 12. A system, comprising: a non-transitory memory; and one or more hardware processors coupled with the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising: obtaining, by a first instance of a stateless application executed in the system, a workflow associated with a user account, wherein the workflow indicates a first task and a second task, wherein the second task is associated with a delayed time; transmitting, by the first instance of the stateless application, a job request to a data processing engine based on the first task indicated in the workflow; submitting, by the first instance of the stateless application to a messaging module, a first message addressed to the stateless application based on the workflow, wherein the first message comprises a reference to the user account and the second task; in response to receiving the first message from the messaging module, instantiating a second instance of the stateless application; and performing, by the second instance of the stateless application, the second task based on the first message. 13. The system of claim 12 , wherein the messaging module comprises a queue having a plurality of messages. 14. The system of claim 13 , wherein the operations further comprise inserting, by the messaging module, the first message in the queue based on the delayed time associated with the second task. 15. The system of claim 12 , wherein the operations further comprise transmitting, by the messaging module, the first message to the stateless application according to the delayed time. 16. The system of claim 12 , wherein the second task comprises a job status inquiry associated with the job request, and wherein the performing the second task comprises transmitting a job status inquiry request to the data processing engine. 17. The system of claim 12 , wherein the second task comprises a status inquiry associated with the user account, and wherein the performing the second task comprises: retrieving, by the second instance of the stateless application, status data indicating a current status of the user account within the workflow; and transmitting, by the second instance of the stateless application, the status data to a second data processing engine. 18. The system of claim 12 , wherein the operations further comprise terminating the first instance of the stateless application after submitting the first message to the messaging module. 19. A non-transitory machine readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising: obtaining, by a stateless application executed on the machine, a workflow associated with a user account, wherein the workflow indicates a first task and a second task, wherein the second task is associated with a delayed time; transmitting, by the stateless application, a job request to a data processing engine based on the first task indicated in the workflow; submitting, by the stateless application to a messaging queue, a first message addressed to the stateless application based on the workflow, wherein the first message comprises a reference to the user account and the second task; and in response to receiving the first message from the messaging queue, performing, by the stateless application, the second task based on the first message. 20. The non-transitory machine readable medium of claim 19 , wherein the messaging queue is external to the stateless application.
Querying (for retrieval from the web G06F16/953) · CPC title
considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration (scheduling strategies G06F9/4881 and subgroups) · CPC title
Allocation of resources, e.g. of the central processing unit [CPU] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.