Repository navigation
[Hyperdrive, Workers] Configure placement near databases - #34186
Closed
irvinebroque wants to merge 3 commits into
Closed
irvinebroque wants to merge 3 commits into
irvinebroque wants to merge 3 commits into
Conversation
github-actions
Bot
added
product:workers
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://bib-hyperdrive-placement-guidance.previews.developers.cloudflare.com (commit 132a0c0)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
irvinebroque
commented
Oct 10, 2026
|
|
||
| <Render file="placement-hint-partial" product="hyperdrive" /> | ||
|
|
||
| The [Hyperdrive configuration API](/api/resources/hyperdrive/subresources/configs/methods/get/) exposes origin connection information, but does not return the database's cloud region. Confirm that region with your database provider. For PlanetScale, refer to [Worker placement for PlanetScale](/hyperdrive/planetscale/#configure-worker-placement). |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| The [Hyperdrive configuration API](/api/resources/hyperdrive/subresources/configs/methods/get/) exposes origin connection information, but does not return the database's cloud region. Confirm that region with your database provider. For PlanetScale, refer to [Worker placement for PlanetScale](/hyperdrive/planetscale/#configure-worker-placement). |
|
|
||
| The [Hyperdrive configuration API](/api/resources/hyperdrive/subresources/configs/methods/get/) exposes origin connection information, but does not return the database's cloud region. Confirm that region with your database provider. For PlanetScale, refer to [Worker placement for PlanetScale](/hyperdrive/planetscale/#configure-worker-placement). | ||
|
|
||
| Placement affects [fetch event handlers](/workers/runtime-apis/handlers/fetch/). It does not place RPC methods or named entrypoints. Refer to [placement limitations](#placement-behavior) before choosing an application architecture. |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| Placement affects [fetch event handlers](/workers/runtime-apis/handlers/fetch/). It does not place RPC methods or named entrypoints. Refer to [placement limitations](#placement-behavior) before choosing an application architecture. |
Contributor
|
@irvinebroque This draft pull request has had no activity for 3 days. It will close after 7 days of inactivity. Transition to ready for review if ready. A codeowner can comment |
Contributor
Contributor
|
@irvinebroque This draft pull request has had no activity for 3 days. It will close after 7 days of inactivity. Transition to ready for review if ready. A codeowner can comment |
Contributor
|
@irvinebroque Closing this draft pull request after 7 days of inactivity. Re-open at a later date and transition to ready for review when you are ready if you seek review. |
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
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.
Make explicit region placement part of Hyperdrive setup before deployment for Workers that make multiple sequential queries to a regional database.
Explain how to obtain the database provider and region, why Hyperdrive origin connection information does not automatically establish Worker placement, and how to handle unknown or multiple back-end locations.
Companion skills update: cloudflare/skills#230