Horizontal scaling is here! This is one that we’ve been planning for some time, so we’re ecstatic to get this feature into your hands.
Let’s take it for a spin!
Horizontal Scaling
You can now set number of replicas in your service settingsVertical scaling only goes so far. At a certain point your application runs out of CPU or RAM and then, as they say, what do?
Previously on Railway we offered a workaround using Cloudflare load balancers but our goal was always to have horizontal scaling out of the box.
Now we have it.
Horizontal scaling on Railway has a number of benefits:
- Eliminates a single point of failure for your application, thereby improving availability
- Reduces cost over time as vertical scaling gets expense faster than horizontal scaling
- Enables scaling your application to infinity and beyond
If you’re wondering about load balancing, in this rollout we’re doing round robin load balancing. Since Railway VMs under the hood are similar, the risk of federating a request to a server with less vertical capacity is moot.
To get started, check out the Settings panel in your service where you should now see a Replicas field.
And to learn more, check out the docs.
Logs Are Getting Faster
We’re in the process of migrating our logging service over to ClickHouse to give you the speedy logs that you so desire.
Performance so far is great but we’re slow-rolling this migration to make sure that there are no anomalies.
Stay tuned for more.
Improvements and Fixes
- We cleaned up some lingering CSS issues leftover from the migration to vanilla Tailwind
- We added better explanation text when deleting a successful deployment
- We fixed an issue with dates related to the Templates Kickback program
- We fixed a bug with scroll locking in logs