Patterns
5 videos · 17:00
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.
Videos
1. Patterns 1 · 3:46 Polling and change detection The ERP reports no changes, so every poll fetches all customers, and the video shows how to find out which of them changed.Watched
2. Patterns 2 · 3:05 Sending data to several destinations Three destinations each receive the invoices from one channel, and each destination has its own reader on the invoice channel.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, and singleton: truelets one copy lead while a second copy on another agent stands by.Watched
4. Patterns 4 · 3:47 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. 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
Read in the docs
The Events and Camel integrations groups of the docs have the reference for this track. The videos teach these pages:
- The entity store
Taught in Patterns 1
- Channels
Taught in Patterns 2
- Schedules
Taught in Patterns 3
- Change tracking
Taught in Patterns 4
- One copy at a time
Taught in Patterns 5