Wevo iPaaS process queue¶

Process queues are a method of organizing data sent by a flow. They can sit in the queue until they are integrated into their target systems. The data in a process queue can be used for monitoring, report extraction, and a few other things.

Watch our webinar (in Portuguese) on process queues.

When we talk about integrations, there are several options for data transit solutions. What are the upsides of a data integration method that uses process queues, like the Wevo platform? Let's look at a few of them:

Reliability¶

The presence of a data-storing queue in an integration process can improve its reliability. When data gets stored in a queue instead of being sent directly from one system to another, this prevents data loss in situations when there is sudden, unexpected instability in either one of the two systems while the integration was in progress.

This makes your flows more error-resistant. You can manage reattempts more precisely, and your data becomes traceable. Even if an error does occur, it's easier to identify what happened based on where your data is sitting. Questions like, When was this piece of data received?, When exactly did an error happen?, and Which system did it come from? can be readily answered thanks to the monitoring tools.

Dependency removal¶

This means that your integration won't be dependent on the same-time availability of the two systems being integrated. The process queue allows for asynchronous integration flows. If the target system isn't ready, the data can sit in the queue and wait until it is.

A practical example of this could be an integration between an e-commerce system and an ERP system. All orders are received from the source (the e-commerce system) and sent to the target (the ERP system). If, at any point, the company decides to replace their ERP with another system, it won't be necessary to reconstruct the integration from scratch. Only a tiny adjustment is needed, and most of the existing integration can be reused. This saves time and money that would otherwise be spent in developing.

Granular transaction volume¶

Some systems limit how much data can be processed per run. With the process queue, you can customize the amount of data sent. For instance, imagine that your source system sends 100 orders per run, but your target system is custom-made and can only receive 5 at once. With the process queue, you can control the amount that is sent. While the first five records are sent immediately, the rest can sit in the queue and wait until the target system is ready for them.

Another possible benefit of this feature is if one of your target systems ever needs maintenance, you can stop or interrupt the part of your flow that connects with the target. Depending on how much space is available in your queue, it may not be necessary to stop the first half of the flow at all, the data sent by the source can rest in the queue until the target system is active again. That way, your operation wouldn't be completely halted.

See also our pages on how to create and monitor your process queues.