Thank You Heroku, or "How To Eliminate Sysadminning"
blog.dougpetkanics.com
Thank You Heroku, or "How To Eliminate Sysadminning"
1–10 of 66 posts
Re: Thank You Heroku, or "How To Eliminate Sysadminning"
#2Those are two bold, scary statements.
Re: Thank You Heroku, or "How To Eliminate Sysadminning"
#3Heroku never goes down, and it eliminates the need to pay a sysadmin (or the time value of sysadminning yourself). Those are two bold, scary statements.
Regarding the second though, I truly believe that the cost + time savings are tremendous from using their platform vs administering your own early on in a startup product lifecycle.
Re: Thank You Heroku, or "How To Eliminate Sysadminning"
#4I have had poor results getting customers to use Heroku. I tried twice, and both times the extra cost over running your own EC2 instances convinced my customers to eventually spend much more money having me set up custom infrastructure - not a good decision unless you expect to have a very high volume site (I hope they are not reading this :-)
Re: Thank You Heroku, or "How To Eliminate Sysadminning"
#5Re: Thank You Heroku, or "How To Eliminate Sysadminning"
#6Re: Thank You Heroku, or "How To Eliminate Sysadminning"
#7Is there something like heroku for django apps? :)
Re: Thank You Heroku, or "How To Eliminate Sysadminning"
#8Add php support pretty please
Re: Thank You Heroku, or "How To Eliminate Sysadminning"
#9Heroku is great, no doubt about that. My only issue is the 'guilt factor': almost all of my use of Heroku has been for free (my cookingspace.com web site that I use to monitor my diet because I take blood thinners; test deploying prototypes; used it to write 3 articles about Heroku for DevX). I have had poor results getting customers to use Heroku. I tried twice, and both times the extra cost over running your own EC…
The nebulous cost of more developer and admin time is something they can carefully ignore in their cost calculations.