Synthèse
At a high level, webhooks-processor sits between three worlds: Producers: Atlassian products (Jira, Confluence, Bitbucket) publishing events through an internal publish/subscribe substrate, with a few REST-triggered flows on the side. A two-stage processing pipeline. Event Matching reads from an events queue and writes matched events onto a webhooks queue; Event Delivery drains the webhooks queue and dispatches. Consumers: Forge apps via the Forge runtime, repository-hook recipients at cus
At a high level, webhooks-processor sits between three worlds: Producers: Atlassian products (Jira, Confluence, Bitbucket) publishing events through an internal publish/subscribe substrate, with a few REST-triggered flows on the side. A two-stage processing pipeline. Event Matching reads from an events queue and writes matched events onto a webhooks queue; Event Delivery drains the webhooks queue and dispatches. Consumers: Forge apps via the Forge runtime, repository-hook recipients at customer-controlled URLs, and audit-log endpoints at customer-supplied destinations.
Inside the Events Rail: How Atlassian Delivers 10 Billion Webhooks a Month ↗
atlassian.com · 29 juil.
Producers emit events on shared rails
· 29 juil.
CORTEX