feat(deployment): latency-based multi-region routing for deployment orchestration#851
Merged
temma02 merged 1 commit intoJun 27, 2026
Conversation
…nt orchestration Adds RegionSelectorService which measures user→region and region→Horizon latency for us-east-1, eu-west-1 and ap-southeast-1, selects the region minimising 0.7·user + 0.3·horizon, caches the choice in Supabase with a 5-minute TTL, and falls back to us-east-1 when measurement fails. Closes StellerCraft#757
|
@Manuel1234477 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
2 participants
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 a region selection service that picks the optimal Vercel deployment region based on measured latency, instead of always targeting a single region.
RegionSelectorService(apps/backend/src/services/region-selector.service.ts):getNetworkMetadata).0.7 × user_latency + 0.3 × horizon_latency.region_latency_cache) to avoid re-measuring on every deployment.us-east-1when measurement fails.scoreRegion/selectOptimalRegionkeep the algorithm unit-testable; the latency probe is injectable.region_latency_cachetable (supabase/migrations/014_region_latency_cache.sql).Tests
apps/backend/src/services/region-selector.service.test.tscovers the weighted selection algorithm across latency combinations, the 5-minute cache (hit within TTL, miss when expired), cache writes, and the fallback path.Run:
pnpm --filter @craft/backend test -- region-selectorCloses #757