Implement Multi-Region Deployment Orchestration with Latency-Based Routing Selection

[temma02]

Description

All deployments currently target a single Vercel region. Implement a region selection service that picks the optimal Vercel deployment region based on the user's IP geolocation and measured Stellar Horizon endpoint latency for the chosen network.

Requirements and Context

• Support regions: us-east-1, eu-west-1, ap-southeast-1
• Select region that minimizes: 0.7 × user_latency + 0.3 × horizon_latency
• Cache region selection for 5 minutes to avoid re-measurement on every deployment
• Fallback: if region measurement fails, default to us-east-1

Suggested Execution

Branch: feat/multi-region-deployment-routing

Implement Changes

• Create region-selector.service.ts in apps/backend/src/services/
• Add latency measurement by pinging each region's health endpoint
• Cache results in Supabase with a 5-minute TTL
• Add unit tests for region selection algorithm with mocked latency values

Test and Commit

Run pnpm test -- region-selector and confirm optimal region is selected for various latency combinations.

Example Commit Message

feat(deployment): add latency-based multi-region routing for deployment orchestration

Co-authored-by: <your-name>

Guidelines

• Branch off main, keep PRs focused on one issue
• All new code must include unit or integration tests
• Ensure pnpm lint and pnpm typecheck pass before review
• Link this issue in your PR description
• Request review from at least one maintainer before merging

[OkonkwoEmeka]

@OkonkwoEmeka has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, I’d like to work on this issue.

I understand the goal is to add a region selector that picks the best Vercel deployment region from "us-east-1", "eu-west-1", and "ap-southeast-1" using both user IP latency and Stellar Horizon latency, with the final score weighted as "0.7 × user_latency + 0.3 × horizon_latency".

My approach would be to add "region-selector.service.ts", measure each region’s health endpoint, include Horizon latency for the selected network, cache the result in Supabase for 5 minutes, and fall back to "us-east-1" if measurement fails.

I’ll also add unit tests with mocked latency values to confirm the scoring logic, cache behavior, and fallback path work correctly before opening the PR.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OkonkwoEmeka to this issue.

[Manuel1234477]

@Manuel1234477 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi! I’m a full-stack developer with a strong blockchain background. I’d love to handle this issue and can deliver a clean, reliable solution. Kindly assign it to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Manuel1234477 to this issue.

[drips-wave]

Congratulations, @Manuel1234477! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Manuel1234477: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Manuel1234477 as part of the Stellar Wave Program's 6th Wave 🥳

😎 @Manuel1234477: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.