Heroku vs VPS Price

I will create a rail application that will mainly serve the files uploaded by the user (not so much, say, a maximum of 1 MB per client) for several facebook applications (iframes).

I am not sure which route I should take. Now I'm looking at the hero + Amazon S3, not VPS. I know that the heroku / amazon route is a little expensive, but I have 0 deployment / scaling experiences, and although I am not opposed to learning new things, I am worried that this might be too much for me, given that I am starting from design / front development background.

What do you guys think will work better in this case?

+7
source share
2 answers

I would recommend Heroku / S3. As long as you are dealing with "not very large" disk space and without using a central processor (for example, video en / decoding), you should stick to the simplest solution and go in a pragmatic way. This is most likely Heroku / S3.

I run my application (similar to your usecase, just a few images per user) on Heroku / S3, and my monthly bills go below the McDonald menu every week.;)

+5
source

If you do not work with tiny margins and large-scale, I would not worry about the “slightly more expensive”. Go down the easiest route, make it work and worry about saving a percentage later when you know how much it can cost you.

+6
source

All Articles