Shared worker pool across queues

warningshared-worker-pool-across-queues

One worker pool consuming several queues lets a slow or poisoned queue starve the others. That is precisely what the design's per-queue isolation requirement forbids.

Severity: warning
Selects: every node of kind worker
Components in scope: 83

What it checks

It looks at every node of kind worker, and fires when:

— all of these hold:
— the node has more than 1 incoming edge from a queue
— the design requirement `isolation.perQueue` is true

Message

Worker '{{node.id}}' consumes more than one queue while the design requires per-queue isolation. Give each queue its own worker pool.

{{node.id}} style paths are filled in from the node, the edge or the design the finding is about.

Applies to · 83 components

Worker worker

Tripped by · 9

Reference designs whose broken twin names this rule in its header. The gate reads the same header, and fails when a rule no design trips.

canva-uploadsreference distributed-emailreference duolingo-backendreference gitlab-architecturereference meta-threadsreference pinterest-feedreference reddit-feedreference slack-messagingreference wikipediareference

Source

1# yaml-language-server: $schema=../schema/rule.schema.json
2# One worker pool consuming several queues means a slow or poisoned queue starves the
3# others, which is exactly what the per-queue isolation requirement forbids.
4# Tripped by: designs/slack-messaging.broken.yaml
5schemaVersion: "1"
6type: "rule"
7id: "shared-worker-pool-across-queues"
8severity: "warning"
9select:
10  node:
11    kind: "worker"
12when:
13  all:
14    - hasEdge:
15        direction: "in"
16        peerKind: "queue"
17        count:
18          gt: 1
19    - requirement: "isolation.perQueue"
20      equals: true
21message: "Worker '{{node.id}}' consumes more than one queue while the design requires per-queue isolation. Give each queue its own worker pool."

The same page as markdown, for an agent: /catalogue/rules/shared-worker-pool-across-queues.md