Railway offers some quick and easy ways to configure deployments for achieving optimal performance.
Specifically, we offer the following features:
- Horizontal Scaling with Replicas (vertical scaling is done automatically)
- Regional Deployments
Continue reading for information on how to configure these.
Scale horizontally by manually increasing the number of replicas for a service.
To change the number of replicas per deploy within your service, go to the service settings view and look for the "Replicas" field in the "Deploy" section. This will create multiple instances of your service and distribute traffic between them.
Each replica will be deployed with a Railway-provided environment variable named
RAILWAY_REPLICA_ID which can be used for logging and monitoring, for example.
At the moment, Railway will round-robin requests to the replicas of your service. We plan to add more advanced load balancing strategies in the future. If you need more advanced load balancing, you can use an external load balancer such as Cloudflare to distribute traffic between your services.
Note: For now Railway does not support sticky sessions nor report the usage of the replicas within the metrics view.
Railway's infrastructure spans multiple regions across the globe, and by default Railway deploys to
us-west1 located in Portland, Oregon.
To choose a different region for your service, go to your service settings and select the desired region -
Additional regions may be added in the future as Railway continues expanding its infrastructure footprint.
For information on the impact of changing a service's region, see the Regions reference guide.
By default, Railway maintains only one deploy per service.
Edit this file on GitHub