Posting a reply: one transaction, then outbox and wake-ups

Posting a reply: one transaction, then outbox and wake-ups A data-flow diagram generated by Archify. 01 / Request 02 / Check 03 / One transaction 04 / Wake-up and relay 05 / Side effects Member browser · POST /api/topics/:id/replies · 01 / Request Member browser POST /api/topics/:id/replies user-api · Origin, CSRF, plugin filters, can() · 02 / Check user-api Origin, CSRF, plugin filters, can() core.posts · post, counters, search tsvector · 03 / One transaction core.posts post, counters, search tsvector core.events · outbox row, IDs only · 03 / One transaction core.events outbox row, IDs only core.cache_tags · topic, forum, member versions · 03 / One transaction core.cache_tags topic, forum, member versions workers relay · every 1 s, SKIP LOCKED · 04 / Wake-up and relay workers relay every 1 s, SKIP LOCKED NOTIFY · sent on commit, wake-up only · 04 / Wake-up and relay NOTIFY sent on commit, wake-up only Notifications · email + push, can() re-checked · 05 / Side effects Notifications email + push, can() re-checked Webhooks · signed, SSRF-safe fetch · 05 / Side effects Webhooks signed, SSRF-safe fetch Plugin events · plugin-host /internal/events · 05 / Side effects Plugin events plugin-host /internal/events CDN purge · visibility changes only · 05 / Side effects CDN purge visibility changes only Tag listeners · every process: stale HTML misses · 05 / Side effects Tag listeners every process: stale HTML misses reply markdown post + counters post.created bump tags claim rows pg_notify(tag) reload versions pg-boss job pg-boss job pg-boss job if visibility Legend primary data async batch data store data flow