4 ms·
This article resonated with me, but the main reason I moved from RoR apps to JS/SPA was hosting costs and scalability. I can build a SPA and host the bulk of it
by 20wenty 5y ago
This article resonated with me, but the main reason I moved from RoR apps to JS/SPA was hosting costs and scalability. I can build a SPA and host the bulk of it on Amazon S3 and pay significantly less monthly costs AND have scalability built in. If you've figured out a way to do something remotely similar with Rails, I'd be back in a heartbeat.
- gls2ro 5y agoI think you meant to say that you can build the front end of an RoR app in JS/SPA and host it on S3. Because it is hard for me to see how you can create a backend API in JS and host it on S3. I might be wrong as my knowledge in JS is limited.
- 20wenty 5y agoRight, front end on S3 built in something like React, and API/backend on other services. There are established patterns like https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/deploy-a-react-based-single-page-application-to-amazon-s3-and-cloudfront.html https://docs.aws.amazon.com/prescriptive-guidance/latest/pat... and https://docs.aws.amazon.com/whitepapers/latest/serverless-multi-tier-architectures-api-gateway-lambda/single-page-application.html https://docs.aws.amazon.com/whitepapers/latest/serverless-mu..., but looking at the diagrams supports OP's point: "it so much harder to create apps in the JavaScript ecosystem."