The key difference between synchronous and asynchronous data transactions is that synchronous communication is scheduled, real-time interaction while asynchronous transactions happen on their own time and don’t need scheduling.
Within the context of Alumio, this means that we deliver real-time data synchronisation between systems thanks to HTTP Proxies and Webhooks, or we deliver asynchronous transactions using our extensive scheduler options, giving users the customisation tools necessary to create their own synchronisation processes within Alumio.
The majority of the integrations built using Alumio are asynchronous. This means that data is fetched and processed in the background. Because of this reason, most of your integrations will require you to configure one or more scheduled jobs. Scheduled jobs instruct Alumio to execute a process at a set schedule.
This means that the data is being synchronized in the background and that there are two steps to each integration: filling the queue and processing the queue. In some cases you may opt to go with a real-time processing integration, essentially reducing the process to a single step: filling the queue and immediately processing it.