Internal networking should prioritize the current region
mhornbacher
PROOP

8 hours ago

Having .railway.internal prioritize the current region in the load balancer would be an incredible unlock for global fast services.

For example I have a service that uses a Caddy proxy to pick the final service by path (e.g. /app, /blog) this is to keep it all on one SEO sitemap and target (backlinks to the /blog pages should improve the ranking of the landing pages and vice versa). While the caddy reverse proxy can be scaled across regions (this is nice! Thank you 🙏) services that would benefit from being regional (e.g. PowerSync API containers, NextJS Pre-Rendered pages, frequently updated SPA bundles) could get the benefits of being regional while having a failover to other regions under load.

The current "it is not forced to the same" region is great for regional redundancy and load balancing but if it could be strongly weighted towards them (perhaps a latency penalty in the LB) that would make it the killer multi-region product!

Under Review

0 Threads mention this feature

0 Replies

Welcome!

Sign in to your Railway account to join the conversation.

Loading...