Events
Weik.io 2026.2Connect integrations through channels, bring events in with event sources, deliver them with CloudEvents attributes, resend dead letters, track database changes and keep state in the entity store.
On this page
Events let integrations work together without knowing about each other. One integration publishes “an invoice was created” into a channel, and any number of others react to it, now or later, on any agent of the same environment. A channel with a type delivers its events to Slack, S3, SFTP, Kafka, JMS, HTTP or any other Camel sink, and an event a reader fails on ends in the dead letters, where you send it again. Every stored event also carries its CloudEvents 1.0 attributes.
These pages follow the invoice-created channel of the finance project, from the integration that publishes into it to the readers, the deliveries and the dead letters. The last two pages cover change tracking, which publishes database changes into a channel, and the entity store, which remembers what an integration has already processed.
An event source brings events in from an external system with a Camel source kamelet, such as a queue, a bucket, a webhook or a folder. A subscription binds the source to a channel and can filter or transform the events on the way. The channel invoice-created carries every event with its CloudEvents 1.0 attributes to its readers, the integrations invoice-notify and invoice-archiver. A channel with a type also delivers its events to Slack, S3, SFTP, Kafka, JMS or any HTTP endpoint.
Pages#
weikio deadletters resend sends it to its reader again once you have fixed the cause.Change tracking A change tracking integration captures a database's changes with Debezium and publishes every insert, update and delete into a channel.The entity store Integrations remember what they have processed in the entity store with entitystore-sink, react to changes with entitystore-source, and read back revisions and records.