Parallel processing in cloud

A method based on a plurality of cloud instances, comprising:

• adding, by a task management server and to a task queue, a task wherein the adding comprises:
• initializing a first type of token corresponding to a first request, wherein the first type of token comprises a null character;
• adding the first type of token to the task queue with the first request;
• sending, by the task management server, a first message to a first cloud instance, of a plurality of cloud instances, to initiate performing of the task;
• receiving, by the task management server and from the first cloud instance, a request to add one or more sub-tasks, of the task, to the task queue;
• adding, to the task queue, the one or more sub-tasks wherein the adding comprises:
• initializing a second type of token corresponding to a second request, wherein the second type of token comprises a non-zero numeric character;
• adding the second type of token to the task queue with the second request;
• and
• sending, by the task management server, a second cloud instance of the plurality of cloud instances, a second message to initiate performing of the one or more sub-tasks concurrently with performing of another sub-task of the task by the first cloud instance;
• receiving, by the task management server, from the first cloud instance and based on an expiration period associated with the performing of the task or the performing of the one or more sub-tasks, to add, to the task queue, a third request for completing the performing of the one or more sub-task
• wherein sending the first message further comprises sending the first type of token to the first cloud instance, wherein the first type of token is determined based on the adding of the task to the task queue,
• wherein receiving the request comprises receiving, from the first cloud instance, the second type of token, wherein the second type of token is determined based on the performing of the another sub-task by the first cloud instance,
• wherein sending the second message further comprises sending the second type of token to the second cloud instance;
• wherein the first request comprises data associated with the task and the data is represented in a tiered data structure comprising at least a first tier and a second tier;
• wherein the indication that the first cloud instance is performing the one or more sub-tasks, of the task, comprises an indication that the first cloud instance is processing data of the first tier;
• and
• wherein the second request comprises a request to process data of the second tier.

A method comprising:

• receiving, by a task management server, a first request to perform a plurality of tasks;
• initializing a plurality of task queues for the plurality of tasks, wherein the initializing comprises:
• selecting, a first task from the plurality of tasks;
• adding, the selected first task to a task queue, wherein the adding comprises:
• initializing a first type of token corresponding to a first sub-task of the first task, wherein the first type of token comprises a null character;
• adding the first type of token to the task queue with the first sub-task;
• causing, by the task management server and based on the adding of the first task to the task queue and the adding of the first type of token to the task queue with the first sub-task, a first cloud instance, of a plurality of cloud instances, to initiate performing of a first sub-task of the selected first task, wherein initiating performance on the first cloud instance comprises:
• assigning the first sub-task and the first type of token to the first cloud instance based on availability of the first cloud instance;
• creating the first cloud instance specifically for execution of the first sub-task;
• requesting, by the first cloud instance, the first sub-task and the first type of token from the task management server;
• receiving, by the task management server and from the first cloud instance:
• an indication to add tasks for performing other sub-tasks to the task queue;
• adding, to the task queue, a second sub-task of the first task, where in the adding comprises:
• initializing a second type of token corresponding to the second sub-task,
• wherein the second type of token comprises a non-zero numeric character;
• adding the second type of token to the task queue with the second sub-task;
• and
• causing, by the task management server and based on the adding of the second sub-task to the task queue and the adding of the second type of token to the task queue with the second sub-task, a second cloud instance, of the plurality of cloud instances, to initiate performing of the second sub-task concurrently with the performing of the first sub-task;
• and
• receiving, by the task management server, from the first cloud instance and based on an expiration period associated with the performing of the task or the performing of the first sub-task, to add, to the task queue, a third request for completing the performing of the first sub-task
• wherein receiving the indication further comprises receiving the first type of token, wherein the first type of token is determined based on adding of the first sub-task to the task queue,
• wherein initiating the performing of the first sub-task further comprises determining, based on the performing of the first sub-task, the second type of token;
• wherein the first request comprises data associated with the task and the data is represented in a tiered data structure comprising at least a first tier and a second tier;
• wherein the indication that the first cloud instance is performing the first sub-task, of the first task, comprises an indication that the first cloud instance is processing data of the first tier;
• and
• wherein the second request comprises a request to process data of the second tier.