DEV Community

loading...

Discussion on: Deploying a Production-ready React-Express app on AWS

Collapse
vitalykarasik profile image
Vitaly Karasik • Edited

1) Regarding NodeJS - as @moviemaker93 wrote, with Elactic Beanstalk you can deploy backend in the "Heroku style"
2) As for React FE - the best practice is deploy to S3. It's static site after all.

why would any startup prefer aws over heroku/netlify/glitch/etc

AWS is providing much more services and flexibility. Plus it's cheaper.

Collapse
rtivital profile image
Vitaly Rtishchev • Edited

1) okay, tomayto, tomahto, no pros for aws here anyway
2) best practice to deploy static apps to s3? Well, maybe if you have it fully set up in aws, for someone who has, not there is no reason to choose it over netlify/gh-pages

AWS is providing much more services and flexibility. Plus it's cheaper.

I did not say aws does not provide value. I said that aws is too complicated and for startup it will always be easier to work with saas solutions that either cost nothing or dirt cheap. AWS will always be for those who have devops or at least a very skillful backend engineer that can dedicate some time to setup deployments

Thread Thread
vitalykarasik profile image
Vitaly Karasik • Edited

for startup it will always be easier to work with saas solutions

AWS has a lot of services, and this article is using the IaaS, while there are many SaaS solutions from AWS.
IMHO, Heroku is nice for MVP/PoC or side projects, but on the next steps company should go to AWS/GCP.

PS: unfortunately, I'm not getting $$ from AWS :-(

Thread Thread
rtivital profile image
Vitaly Rtishchev

Heroku is nice for MVP/PoC or side projects

That's what i meant.

Although in my company we still use heroku for half of web applications deployments. It is still cheaper at at larger scale to buy dynos than to either lose developers time with aws or devoting someone with aws knowledge.