3 days ago
Hi Railway Team,
I hope you are doing well.
We are currently evaluating Railway as a potential platform for migrating our existing infrastructure from AWS. At present, our applications are hosted on AWS EC2 with a Docker-based microservices architecture, and we are interested in understanding how Railway can support our deployment and scaling requirements in a more streamlined and cost-effective manner.
Our current environment includes:
Multiple Node.js and FastAPI microservices
Dockerized applications
API Gateway architecture
We would like to know:
The best approach for migrating our complete infrastructure from AWS to Railway
Recommended architecture and deployment strategy on Railway
Estimated pricing and cost optimization suggestions for our use case
Best practices for handling production-grade microservices on Railway
Any limitations or recommendations compared to AWS-based deployments
Support for internal networking, databases, scaling, and monitoring
We are particularly interested in understanding whether Railway would be suitable for hosting our production workloads and how it compares cost-wise against maintaining dedicated AWS EC2 infrastructure.
We would appreciate any guidance, documentation, or recommendations from your team regarding migration planning and platform suitability.
Looking forward to your response.
Best regards,
Nikil B B
0 Threads mention this feature
1 Replies
2 days ago
don't migrate, we regret coming to railway. Shit platform always down and can't deploy