:fingers crossed:
Why, because the other providers (or a roll-your-own solution) will not have outages?
Or because the customers cannot tolerate even the more or less half a day of outage per year AWS has?
Even critical businesses like banking have work stoppages far more often than that for tons of reasons, in both the physical world and the digital/networked one.
Heroku does make a lot of sense: it's an abstraction. You're using a system designed to do a lot of the heavy lifting so you don't have to deal with those details, and for many startups and small operations, it's a great value proposition.
But you have to admit that it is only a value proposition; and fundamentally a tradeoff. The truth is, especially from the perspective of a seasoned operations manager, all of the things above are just not that hard, nor are any of the complaints outlined in the OP article.
The more layers you put between you and your infrastructure, the harder it will be to control your availability. When EBS's start failing and you have no idea why and Amazon only shows a green dot on their status page with a cryptic message like "minor availability issues experienced in certain availability zones; investigating." Now that is hard.
Cloning a server and keeping a mirrored backup in another data center if you really need the availability? On hardware you have full control over? Not that hard. http://whoownsmyavailability.com/
First the UI could use some work, but it was really awesome seeing it pull down a Flask app and knowing to activate venv and install pip.
Also, not having an option to delete your account is a bit scary, seeing as I'm part of an organization on github and not comfortable with you having access to that code.
There is an option to delete your account. One option is to contact us (I know, that's not great, but we delete same day). The other option is to rip out Circle's authentication via GitHub, if you're worried about us doing it properly.
Heroku seems to be like a more useful Google App Engine, a good place to host a blog or experimental project if you're not into dev-ops.
If you have a knack (at all) for dev-ops, you're not saving yourself anything.
The downtime is pretty bleh too. The moment you start doing multi-provider to offset this, you'll end up doing all the dev-ops work you would've had to have done before. Except now, you have to do it all at once in a time of what is probably high stress.
If you do the dev-ops/automation yourself from the start, you can start small/simple and grow that as you go, deploying your services to arbitrary hosting providers (EC2, Linode, dedicated boxes, whatever).
This is why whenever anybody asks me my opinion of Heroku, I respond, "it's a great place to host that blog engine you wrote in Haskell/Clojure/{hipster_language_of_choice}".
There are a ton of real sites that never see more than a couple hundred thousand visitors a month. E-commerce sites, mobile APIs, SAAS apps, etc. I've used Heroku for higher traffic sites than this without any issues at all. Incredibly easy actually.
Saying it's only good for your hipster blog? C'mon man really? Have you even done anything commercial / critical on their platform?
You could host a B2B app no problem, because they are paying (high margin) customers, and will probably not use too many resources.
Agree. Those people who tell horror stories about Heroku/EC2, usually give solid numbers, i.e. this was how much I spent, this is how much I save by moving away, and our response time is now X% faster.
On the other hand, we have article like this that shows pretty graph for a web app serving 16.2 requests per minute, and make bold claims that everything will scale.
https://api.playtomic.com/load.html
Savings aren't exclusively because of Heroku, I also switched the underlying architecture during that migration from C# / ASP.NET to NodeJS which is exceptionally well suited to what I'm doing there.
Previously: Dedicated servers, ~$1600 a month
8x dedicated servers at ~$200 each, each running 3 to 5 instances of the API depending on how many IP addresses they were provisioned with. Uploading was done via a simple hand-rolled script that'd just FTP everything to each server.
Now: Heroku, current usage $400 - $500 a month
With Heroku I don't have to worry about concurrent connections (typically 200 - 400 thousand people at once), I don't have to maintain all those servers and I don't have to fuck around with all the stupid things that can go wrong when you're operating at scale.
It was a lot of work to get to this point and I made a lot of mistakes like having a heavy redis pub/sub outside of the EC2 network that cost me $350 in excess bandwidth providing inter-dyno communication, and I saturated database connections lots of times because in the old days those dedicated servers each had a local mongodb which could keep up with ordinary connection pooling, but it was totally worth it.
It's not that I don't believe you, I just think you don't understand what you're saying.
(Actually, it is that I don't believe you)
That said, if this is if you're doing 500 requests/sec (that's very different than 500 concurrent users) per dyno, good for you. My main bottleneck was not so much CPU on the web machines (I hit memory limitations), but the database layer.
There are lots of different bottlenecks waiting for people operating at scale. Heroku and NodeJS, for my use case, eventually alleviated a whole bunch of them very cheaply.
In the last minute ~460,000 of those requests were made which means somewhere around 230,000 people sent data although there's room for that to be higher or lower depending on sessions starting, sessions ending, and just what period of time you want 'concurrent' to live within.
I said this and was talking exclusively about this. Read my original comment.
Was it written in TCL? ;)
Who said I'm using postgres? And if you don't like the postgres setup, sure, roll your own. EC2 has those badass SSD instances for you.
Apps' that need more capacity then what Heroku offers can surely drop the dev-ops dollars. Until then, why waste your time?
Considering Heroku is single-homed, I find it hilarious that you say it's less of a toy than GAE.
But yeah, the single-homing is pants-on-head.
You can always host your App Engine application on top of an AppScale or Typhoonae install.
I wish they were easier to set up, but, if your Google bill starts getting high, you can dedicate the resources required to do it. And multi-homing them is a whole different game.
This comes up all the time with my company. We make hosted Continous Integration (https://circleci.com), and often hear "can't I just set up Jenkins?". And the answer is the same, "you could, but ...". Run it on EC2, where your tests fail because the IO is bad? What about when three people push at once and you want to get results ASAP? Are you going to manually compile Postgres 9.1? And again when you add a second box to you cluster?
I could go on.