Skip to content

Add article: Reordering an Unordered Azure Service Bus Stream with PowerShell - #189

Open
eosfor wants to merge 1 commit into
PowerShellOrg:mainfrom
eosfor:article/service-bus-stream-reordering
Open

eosfor wants to merge 1 commit into
PowerShellOrg:mainfrom
eosfor:article/service-bus-stream-reordering

Conversation

@eosfor

@eosfor eosfor commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

Summary

This article explores a PowerShell approach for turning an out-of-order Azure Service Bus stream into ordered, session-aware output.

  • Uses message deferral as broker-backed payload storage.
  • Uses session state as a compact ordering index.
  • Walks through the input sequence 1, 3, 4, 2 and the resulting ordered output.
  • Includes two terminal screenshots and a complete terminal screencast.
  • Clearly separates the demonstrated state machine from production guarantees and discusses atomicity, concurrency, gaps, duplicates, and recovery.

Validation

  • Rebased the article commit onto the current upstream/main before submission.
  • Updated the filename and front matter to the September 14, 2026 publication date.
  • Verified the pubs repository and linked script on the current public main branch.
  • Started the Azure Service Bus Emulator with Docker Compose, built the module in Release mode, and reproduced the article flow with a unique session: input 1,3,4,2 produced output 1,2,3,4 with bodies event-1 through event-4.
  • Inspected both screenshots and verified all three published media paths in generated HTML.
  • git diff --check and npm run build passed locally.
  • The branch diff contains only the article and its three media assets.

@netlify

netlify Bot commented Sep 14, 2026

Copy link
Copy Markdown

👷 Deploy request for powershellorg pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit c8678f8

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