Blendr.io knowledge base

Overview of Design Patterns

Design patterns for data synchronization Blends - overview

This chapter describes good practices or "patterns" to design Blends 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 Blend
  • Triggered Blends (Webhooks)

Scheduled Blends

Blend 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 Blends (Webhooks)

Blends 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.

Updated 5 months ago

Overview of Design Patterns


Design patterns for data synchronization Blends - overview

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.