Events
6 videos · 20:50
One integration publishes invoices to a channel and others react to them. The videos build up that invoice example from the channel itself to event sources, subscriptions, delivery to an outside system and dead letters. Camel 1, 2 and 5 are enough background for this track.
Videos
1. Eventing 1 · 3:49 The channel: one integration publishes, another reacts A channel is a name that two integrations share, so that one publishes invoices and the other reacts to them.Watched
2. Eventing 2 · 3:26 An event source brings events in An event source brings events from a system outside Weik.io into a channel named after the source.Watched
3. Eventing 3 · 3:41 A subscription binds source to channel An event subscription binds one source to one channel, so the source's events reach the integrations that read that channel, with no route to write.Watched
4. Eventing 4 · 3:12 Delivery: give a channel a type A channel with a type also delivers its events to a system outside Weik.io, in this video an accounting system that receives each invoice over HTTP.Watched
5. Eventing 5 · 3:21 On the way: filter and steps A filter decides which events an event subscription passes on, and a step changes each event before it reaches the channel, in this video by turning a JSON body into fields.Watched
6. Eventing 6 · 3:21 Dead letters When delivery to a receiver keeps failing, the event becomes a dead letter that records its reader and the reason, and you can send it again.Watched
Read in the docs
The Events group of the docs has the reference for this track. The videos teach these pages:
- Channels
Taught in Eventing 1
- Event sources
Taught in Eventing 2
- Subscriptions, filters and steps
Taught in Eventing 3 and Eventing 5
- Delivery and CloudEvents
Taught in Eventing 4
- Dead letters
Taught in Eventing 6