Im currently a customer at Railway, we have an application that runs on alot of operations, multi managing accounts. I was wondering if Fly.io would be possibly better for us. We experience some downtime every 2 weeks. our current operation runs on 15 instances / 5 redis DBs and MongoDB.
What are the PROs of Fly.io in comparisson to Railway?
Railway is quite costly and we’re not able to use the RAM + CPU they claim they deliver, the instance will heap out of memory and die at 50% of usage.
If latency would not be onerous, maybe you could create an instance of your app in Fly, and then wire it into your LB and DB. That should not be much work, and you then can look at CPU/memory/reliability metrics across the two providers.
Fly has had some teething problems, and a couple of hopping-mad customers, but the view from employees is that the brittle parts are giving way to more reliable replacements.
