docs(internal): add multi-region blog post draft - #3874
Draft
TooTallNate wants to merge 1 commit into
Draft
Conversation
Contributor
|
Contributor
Sim WorldSimulated world deterministic testing for races. Traces 🟠 world-sim scenario book — 1 fail of 41 total
Full trace: |
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
Adds an internal draft of a technical blog post, "The ID is the routing table: how Workflow went multi-region", to the preview-only
docs/internalsection for iteration before publication.The post covers:
@workflow/world-vercel/run-id(tag bit + 6-bit region ID + 5-bit version), why the metadata sits at the top of the randomness section (preserves monotonic ordering), and the frozen append-only region tablestart({ region })→VERCEL_REGION→iad1), legacy untagged IDs decoding toiad1, and per-send queue routing decoded from the run IDProse follows the Vercel technical writing guidelines.
Changes
docs/content/docs/v5/internal/multi-region-blog-post.mdx: the draftdocs/content/docs/v5/internal/meta.json: register the pageNotes
internalsection is preview-only (hidden in production, excluded from sitemap/robots), so this is not publicly visible