Skip to content
Weik.ioPreview

Preview of the text for the YouTube playlist “Patterns”. The service shows it in its own layout.

Patterns

Weik.io

Playlist · 5 videos · 16:43

Problem-first videos: polling, several destinations, schedules, database changes and one copy at a time. From Weik.io University, where each video page lists its commands and the docs pages it teaches: https://weik.io/university/patterns/ Weik.io: https://weik.io Docs: https://weik.io/docs University: https://weik.io/university Weik.io Cloud: https://weikio.cloud Live demo: https://demo.weik.io GitHub: https://github.com/weikio/weikio
  1. 13:37

    Polling and change detection (Patterns 1)

    Weik.io

    With no change timestamps in the ERP, every poll reads all customers, and the hub's entity store lets only new and changed ones reach the CRM. It assumes the Camel track.

  2. 23:04

    Sending data to several destinations (Patterns 2)

    Weik.io

    Each of three destinations gets its own reader on the invoice channel. While the archive is down, accounting and billing keep receiving invoices, and the archive's copy waits in Weik.io.

  3. 33:15

    Running an integration on a schedule (Patterns 3)

    Weik.io

    A cron in the route runs the hello integration at set times, and one line lets one copy lead while a second copy on another agent stands by. Each environment holds its own cron value.

  4. 43:49

    React to database changes (Patterns 4)

    Weik.io

    A change tracking publishes each change to a database table into a channel, where a watcher route reacts to it. The database's administrator has to switch on its change feature first.

  5. 52:58

    One copy at a time (Patterns 5)

    Weik.io

    A job that polls a system must not run twice, even on two agents. One line in the integration's file lets one copy lead, and a standby takes over when the leader's agent stops.