Events
Weik.io
- 13:41
The channel: one integration publishes, another reacts (Eventing 1)
Weik.io
A channel is a name two integrations share, so one can publish invoices while the other reacts. The project declares the channel first, and the channel stores the events that pass through it.
- 2
3:17An event source brings events in (Eventing 2)
Weik.io
An event source reads a system outside the platform and publishes into a channel of its own name. One YAML document is the whole source, and the platform runs it like any integration.
- 3
3:16A subscription binds source to channel (Eventing 3)
Weik.io
An event subscription binds one source to one channel, so events from an event source reach the integrations that read that channel. The platform builds the route itself.
- 4
2:59Delivery: give a channel a type (Eventing 4)
Weik.io
A channel with a type delivers its events to a system outside the platform as well, here an accounting system that receives each invoice over http. The platform generates the delivery route itself.
- 5
3:09On the way: filter and steps (Eventing 5)
Weik.io
A filter decides which events an event subscription passes on, and a step changes each event before it reaches the channel, here by turning a JSON body into fields.
- 6
3:20Dead letters (Eventing 6)
Weik.io
When delivery to a receiver keeps failing, the event becomes a dead letter that has its reader and the reason it failed, and it can be sent again. It builds on the channel delivery from Eventing 4.