Skip to content

Docs: local queues use System.Threading.Channels, not TPL Dataflow - #4411

Merged
jeremydmiller merged 1 commit into
mainfrom
docs-channels-not-dataflow
Sep 10, 2026
Merged

jeremydmiller merged 1 commit into
mainfrom
docs-channels-not-dataflow

Conversation

@jeremydmiller

Copy link
Copy Markdown
Member

Wolverine 5.0 replaced TPL Dataflow with System.Threading.Channels for all of its in-memory queueing. The 5.0 migration notes say so, and JasperFx's Block<T> is built on Channel<T>. Three pages still described the old Dataflow internals:

  • guide/messaging/transports/local.md: the intro, and the "Configuring Parallelization and Execution Properties" section
  • guide/runtime.md: the buffered endpoints description
  • guide/durability/index.md: the outbox message relay description

The only Dataflow mentions left are intentional: the historical 5.0 notes in migration.md, and a "(Wolverine used TPL Dataflow for this before 5.0)" aside on the local queue page.

This PR only changes docs. The local queue page has a related doc problem, filed as #4410: CircuitBreaker() on a buffered local queue is silently ignored.

🤖 Generated with Claude Code

https://claude.ai/code/session_01UPRfTmSLt2W8XBEEtReGab

…ls, not TPL Dataflow

Wolverine 5.0 replaced TPL Dataflow with System.Threading.Channels for all in-memory
queueing (see the 5.0 migration notes), but the local queue, runtime, and durability
pages still described the old Dataflow internals.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UPRfTmSLt2W8XBEEtReGab
@jeremydmiller
jeremydmiller merged commit 7a3e8d7 into main Sep 10, 2026
3 checks passed
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.

1 participant