010101 I've been using Heroku for years now and (to a great extent) I'm familiar with its bottlenecks. In my opinion, I think developers like Heroku because of the fact that it takes away the need for DevOps skills and is more suitable for startups and small teams
Hobby dynos (free tier VPS) are configured to "sleep" when inactive and can only be awoken when a request is sent to it, which can take around 10 - 20s... but this is only if you use a hobby dyno. Paid dynos, although will still be restarted (at least once a day), don't sleep and will respond immediately to any request sent to it. Notwithstanding the fact that free dynos can get annoyingly slow at times, I have a solution I utilize when running on free dynos that make my sites load as if it were running on a paid dyno and it really addresses this issue. My only problem with Heroku is with the cost of scaling.
