Patterns
7 videos · 24:17
You start each video from a problem that integration teams meet, such as an ERP that has no change timestamps or a receiver that goes down, and build the solution with Weik.io. The solutions use the entity store, a reader per destination, schedules, change tracking, integrations that run one copy at a time, a signature check on incoming webhooks and the run records of a scheduled script.
Videos
1. Patterns 1 · 3:47 Polling and change detection Because the ERP reports no changes, every poll fetches all customers.Watched
2. Patterns 2 · 3:05 Sending data to several destinations Three destinations each receive the invoices from one channel through a reader of their own.Watched
3. Patterns 3 · 3:21 Running an integration on a schedule A cron expression in the route runs the hello integration at set times.Watched
4. Patterns 4 · 3:47 React to database changes A change tracking integration publishes every change to a database table's rows, including deletes, into a channel.Watched
5. Patterns 5 · 3:01 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
6. Patterns 6 · 3:58 Handling incoming webhooks The integration acts only on the payment notifications that a bank signs.Watched
7. Patterns 7 · 3:18 Running a script on a cron schedule A schedule runs a script on an agent at set times and leaves logs and a run record for each run.Watched
Read in the docs
The Events and Camel integrations groups of the docs have the reference for this track.
- The entity store
Taught in Patterns 1
- Channels
Taught in Patterns 2
- Schedules
Taught in Patterns 3 and Patterns 7
- Change tracking
Taught in Patterns 4
- One copy at a time
Taught in Patterns 5
- Webhooks
Taught in Patterns 6