Skip to content
Weik.ioUniversity
Try Weik.io

Patterns

5 videos · 16:43

Each video starts from a problem that integration teams meet, such as an ERP that has no change timestamps or a receiver that goes down, and builds the solution with Weik.io. The track uses the entity store, a reader per destination, schedules, change tracking and integrations that run one copy at a time.

Start the trackRead the Events docsRead the Camel docs

Videos

  1. 1. Patterns 1 · 3:37 Polling and change detection Because the ERP has no change timestamps, every poll fetches all customers.Watched
  2. 2. Patterns 2 · 3:04 Sending data to several destinations Each of three destinations gets its own reader on the invoice channel.Watched
  3. 3. Patterns 3 · 3:15 Running an integration on a schedule A cron expression 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.Watched
  4. 4. Patterns 4 · 3:49 React to database changes A change tracking integration publishes every insert, update and delete in a database table into a channel, and a watcher route reacts to each one.Watched
  5. 5. Patterns 5 · 2:58 One copy at a time A job that polls a system has to run as one copy, even when two agents run the integration.Watched

Read in the docs

The Events and Camel integrations groups of the docs have the reference for this track. The videos teach these pages: