Skip to content
Weik.ioUniversity
Try Weik.io

Events

6 videos · 19:42

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.

Start the trackRead the Events docs

Videos

  1. 1. Eventing 1 · 3:41 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. 2. Eventing 2 · 3:17 An event source brings events in An event source brings events from a system outside the platform into a channel of its own name.Watched
  3. 3. Eventing 3 · 3:16 A subscription binds source to channel An event subscription binds one source to one channel, so events from an event source reach the integrations that read that channel.Watched
  4. 4. Eventing 4 · 2:59 Delivery: give a channel a type A channel with a type also delivers its events to a system outside the platform, in this video an accounting system that receives each invoice over HTTP.Watched
  5. 5. Eventing 5 · 3:09 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. 6. Eventing 6 · 3:20 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: