The Decline of Heroku
I still recommend that most startups use Heroku.<p>Engineers always complain about speed and price.<p>If you start comparing ec2 micros to Heroku dynos you already don't understand what Heroku offers.<p>Generally I will see small to medium startups that hire 3 devops engineers who barely have the bandwidth to setup a fully fledged deployment system e.g. pipelines, red/green light deployments, backups, stability etc<p>This all works from the get go with Heroku.<p>Most developers scale resources too early and don't go for easy wins like slow queries and any other latency related problems.<p>How many times have you seen developers recommend upgrading from Ruby to Go because of speed? When all they had to do was add some partial indexes or something to their database.<p>I've shown non technical CEO's in small startups to scale, rollbacks, view logs and restart their servers themselves.<p>I will always pull aside CEO's and tell them that their engineers want the best for the company, but that is only from their vantage point, the likely don't even know the companies inner financials, so how can they tell you something is "cheaper".<p>Focus on your companies core competencies first, get users, make money then let your engineers build their dream devops setup.<p>(If your startup does some mega processing jobs like ML then yeah you will want to use something like EC2)