Skip to content

[Reference Architecture] Update distributed web performance#30589

Open
DavidJKTofan wants to merge 1 commit into
cloudflare:productionfrom
DavidJKTofan:dtofan/update-distributed-web-performance-architecture
Open

[Reference Architecture] Update distributed web performance#30589
DavidJKTofan wants to merge 1 commit into
cloudflare:productionfrom
DavidJKTofan:dtofan/update-distributed-web-performance-architecture

Conversation

…ure with new telemetry fields, shared dictionaries, and tiered cache cloud region hints
@github-actions

Copy link
Copy Markdown
Contributor

Hey there, we've marked this pull request as stale because there's no recent activity on it. This label helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant).

@github-actions github-actions Bot added the stale label May 27, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Hey there, we've closed out this pull request because it's been stale for a while and there's been no additional action on it. If these changes are still relevant, open a new pull request (or flag to us in a GitHub issue).

@cloudflare-docs-bot

cloudflare-docs-bot Bot commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

Review

⚠️ 1 warning found in commit c710a84.

Fan Out Code Review

This code review is in beta and may not always be helpful — use your judgment.

Warnings (1)
File Issue
reference-architecture/diagrams/content-delivery/distributed-web-performance-architecture.mdx line 98 Incorrect Service Bindings usage with Snippets — The text introduces both Snippets and Workers as programmatic customization options, then advises using Service Bindings for communication 'between these Workers'. Service Bindings connect Workers to Workers only; they cannot bind Snippets (which run inline in the rules pipeline) to Workers or to other Snippets. Fix: Clarify that Service Bindings apply to Workers only, not Snippets. For example: 'Use Service Bindings for low-latency communication between Workers when you need multiple Workers to interoperate.'

Style Guide Review

✅ No style-guide issues found.

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command Description
/review Runs a review now. Incremental if a prior review exists, full if not.
/full-review Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/fan-out-review Forces a full review using the per-file fan-out mode regardless of diff size. Each file is reviewed in its own session for maximum per-file detail. ⚠️ This may take a very long time on large PRs and may fail or time out — use only when you want the most thorough review and are willing to wait.
/holistic-review Forces a full review using the holistic mode regardless of diff size. The entire diff is reviewed in one pass, enabling cross-file reasoning. Faster and more reliable on large PRs.
/ignore-review-limit Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants