Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Overview of Design Patterns

This chapter describes good practices or patterns to design automations that perform data synchronization.

We make a distinction between different types of data synchronization:

Scheduling or triggered-based using Webhooks

Data synchronizations need to run on regular intervals, two patterns are possible:

  • Scheduled automations
  • Triggered automations (Webhooks)

Scheduled automations

Automation runs e.g. every minute and processes data incrementally.

Benefit: In the first run, also historic data can be processed (this is impossible with Webhooks).

Limitations: longer intervals can cause delays in data synchronization and increase the risk of conflicts.

Triggered automations (Webhooks)

Automations that are triggered to run each time a change occurs in one of the platforms.

Benefit: minimal delay in synchronization.

Limitations: impossible to process historic data.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!