The Heroku Pricing Gap + Add-on Fever
blog.bryanlanders.com
The Heroku Pricing Gap + Add-on Fever
1–9 of 9 posts
Re: The Heroku Pricing Gap + Add-on Fever
#2AWS only have a temporary free usage tier so collect money right up front even on the smallest projects.
For that reason, these relatively large step functions in pricing at the low end are reasonable from where I'm sitting.
Re: The Heroku Pricing Gap + Add-on Fever
#3Re: The Heroku Pricing Gap + Add-on Fever
#4Remember Heroku have to support millions of users on the free tier on a permanent basis, all of which costs very real cash money compared to your average freemium web business. AWS only have a temporary free usage tier so collect money right up front even on the smallest projects. For that reason, these relatively large step functions in pricing at the low end are reasonable from where I'm sitting.
Heroku is a great deal for people just starting out, somewhat at the expense of those who have already grown larger. His strategy seems sound-- use Heroku at the beginning, then if and when it gets unjustifiably expensive, switch to AWS.
Re: The Heroku Pricing Gap + Add-on Fever
#5Re: The Heroku Pricing Gap + Add-on Fever
#6If I want to upload files, is it necessary to have an Amazon account? As I understand it, you can't use Heroku for dynamic file storage.
Re: The Heroku Pricing Gap + Add-on Fever
#7Heroku is only expensive if your time has no value.
Re: The Heroku Pricing Gap + Add-on Fever
#8The OP undervalues that bit in the TLDR: "stress-free deployment". For us, hiring or contracting a DevOps guy with 1/10th the chops of the heroku crew would cost 10x what we are paying them, and I don't think we'd have a better quality of life. Heroku is only expensive if your time has no value.
Re: The Heroku Pricing Gap + Add-on Fever
#9What kind of traffic could you handle on a 100% free account? Would it be feasible for a low-traffic website, say a few k requests per month? If I want to upload files, is it necessary to have an Amazon account? As I understand it, you can't use Heroku for dynamic file storage.
We're hosting static media on S3, but this project has no UGC and very limited amount of media assets, so you'd have to consider the AWS costs depending on your own needs.
When I first deployed to Heroku, I was serving media right from the web dyno, and it was working, but since the app is serving up the files (not Nginx serving them directly instead, or similar), I'd imagine that's not a great solution in terms of scalability.