News for hackers. Stuff that matters.
Re:I left Heroku for OpsWorks and shaved 40% off response times by grey-area on Saturday February 08, 2014 @09:03AM (#7201191)
Once you have done the setup once and have it all automated, it's more like 1 hour per week keeping on top of upgrades, backups etc. So for many people heroku is an expensive option, even when starting out. Nothing wrong with using it, but outsourcing your infrastructure does not come cheap, compared to other options like a VPS.
Re:I left Heroku for OpsWorks and shaved 40% off response times by Aqueous on Saturday February 08, 2014 @02:06PM (#7202151)
VPS is much more expensive because you have to do all the work to provision (either manually or automatically) the software stack you are working with, configure every new instance either, configure your deployment and testing pipeline using a CI server and using git hooks, and keep the whole edifice up and running. The time overhead is very large, and it ends up taking over as the major cost driver.
Re:I left Heroku for OpsWorks and shaved 40% off response times by grey-area on Saturday February 08, 2014 @03:06PM (#7202428)
Having done most of the steps you mention above for multile clients, I'd contend the time overhead is not very large - most things can be automated, and once that is done an extra instance is just a matter of spinning up a server and deploying - also you can scale a very long way on one or two instances when the hardware is beefy enough (e.g. this website), backup, deploy, testing can all be automated. There are definitely some situations where a service like Heroku or AWS makes a lot of sense, but it can get expensive very quickly; you're trading time to setup/manage for higher ongoing costs forever. VPS is cheaper but requires some setup. That's a trade-off each company has to evaluate individually given the talent and money they have.