Open
Conversation
Explains the relationship between TemporalWorkerDeployment and Task Queues. Multiple task queues can be grouped in a single TWD by running multiple containers (each polling one queue) in the same pod. Splitting into separate TWDs is an optimization when queues have different scaling requirements or deployment cadences. Co-Authored-By: Claude Opus 4.5 <[email protected]>
bchav
force-pushed
the
docs/twd-architecture-diagram
branch
from
183f4f2 to
1a88982
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/task-queues.mdexplaining the relationship between TemporalWorkerDeployment and Task QueuesWhy
Users are asking whether a single TWD can handle multiple Task Queues, or if each TWD should map to a single worker instance. This doc clarifies:
Checklist
🤖 Generated with Claude Code