Skip to content

docs: Message Queue - #1682

Merged
fajinyuan merged 8 commits into
mainfrom
message-queue-documentation
Oct 21, 2026
Merged

fajinyuan merged 8 commits into
mainfrom
message-queue-documentation

Conversation

@dan-fernandes

Copy link
Copy Markdown
Contributor

This is my attempt at starting a docs page for the message queue.

@dan-fernandes
dan-fernandes requested a review from a team as a code owner September 22, 2026 12:52
@codecov

codecov Bot commented Sep 22, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.41%. Comparing base (66b52cc) to head (bfbc416).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1682   +/-   ##
=======================================
  Coverage   96.41%   96.41%           
=======================================
  Files          49       49           
  Lines        3711     3711           
=======================================
  Hits         3578     3578           
  Misses        133      133           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dan-fernandes dan-fernandes changed the title Document Message Queue docs: Message Queue Oct 2, 2026

@shree-iyengar-dls shree-iyengar-dls left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few small grammar things but lgtm

Comment thread docs/explanations/message-brokers.md Resolved
Comment thread docs/explanations/message-brokers.md Resolved
## Topology
The topology of the message broker is decoupled from Blueapi, and entirely deployment-specific. Nonetheless, the following describe how deployments at DLS are generally structured.

RabbitMQ receives messages from Blueapi via its default topic exchange, `amq.topic`. All messages have the routing key `public.worker.event`, so will be forwarded to all queues bound to `amq.topic` with a compatible routing key (eg. `public.worker.event`, `*.*.event` etc.). No default queues exist, meaning that if no downstream services have registered a queue, all messages will be dropped.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Might be useful to explain briefly what a default topic exchange is?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dan-fernandes any comment on @shree-iyengar-dls 's comment here?

@fajinyuan
fajinyuan added this pull request to the merge queue Oct 21, 2026
Merged via the queue into main with commit a1f860f Oct 21, 2026
20 checks passed
@fajinyuan
fajinyuan deleted the message-queue-documentation branch October 21, 2026 10:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants