How does the Task Queue work?

In this video, we will be looking at the Task Queue.

Chapter: Introduction

Task Queue - Introduction

The heart of Alumio is the ability to queue data and only publish data that is mandatory to enrich a certain endpoint. With this powerful core, it tremendously reduces the chance that your IT systems will be overloaded. Data peaks won't give you a headache.

Within Alumio, everything breaks up into unique tasks. Tasks that give you insight into what is running, how long it takes to process, and what the status of a task is.
By default, no filtering is applied and the tasks will be shown in descending chronological order.

When processing the queue of tasks, this is done in chronological order.
Good to know is that each task is related to a single route. So one route can have many tasks, but a task can only be related to one route.

As explained, the queue is processed in chronological order but only for the given route. This means that the queue is divided into many sub-queues.

Chapter: Task Queue

Task Queue - Task Queue

Now moving onto the current screen, you see a selection of the latest tasks in the current queue.

First, we see the identifier field, this identifier is unique to your integration environment and is used by Alumio to identify a task.

Next, we can see the tasks' entity type. The entity type is a data schema that is standardized in Alumio.

This standardization enables integration specialists to re-use components that are available in the ecosystem to built end to end integrations in a short period.

Next, the entities' identifier is displayed. This is useful for identifying for example a specific order number or product SKU.

The next field displays the current status of the task. A task that sits in the queue waiting to be processed will have the status 'new'. After that, it moves to 'processing'.
Depending on the result it will either be finished, failed, or skipped.

The next field shows the route the task belongs to and then it shows the date it was created and the date the last mutation was done to the task. Last you are given the possibility to retry a task. This can be useful when for example when the task had failed because the destination was down.

Chapter: Task Detail

Task Queue - Task Detail

Clicking through to a specific task opens a new screen which consists of four tabs.
The first tab is repeating the information as seen on the task queue:

  • the task identifier, entity identifier, entity type, the route the task belongs to, its current status, and the timestamps indicating when the task was created and last updated.
  • The next tab shows the data of the entity belonging to the task. For this specific task, we can see the data of a slide in here. Other examples would be a sales order, a customer, or a price update.
  • The third tab shows the import messages. This contains all messages that were created when data was retrieved from a system. As this is a route that is HTTP-based, these messages will contain any request send and requested received by Alumio. When clicking on the details button we can inspect the full response given by the system the data was retrieved from.The fourth tab shows the export messages. This contains all messages that were created when data was published to a system. As this is a route that is HTTP-based, these messages will contain any request send and requested received by Alumio. When clicking on the details button we can inspect the full response given by the system the data was sent to.

With this information you now have a good sense what the Alumio Task Queue looks like and how it works.

Thank you for watching and please check Alumio.com for more information and other product videos.