51–60 of 139 posts
So only use heroku if:
a) Uptime is non-critical & you just don't want to deal with setting up a server b) Uptime is non-critical & You don't know how to set up a server
I don't think the OP is right in general. What if your customer sees Heroku's name, and gets confused? She starts asking questions like: Who is on the other end? Am I in business with X or with Heroku? Who should i call?
This is actually a really good point. I can't find it now, but there's an article floating around somewhere about a government employee in some small town accusing Apache or Debian or some project of being "hackers" because his web server broke and was showing the default "congrats it works!" page instead of the town web site.
Bullshit. It's your fault. I'm your user, you took my money. We're done here. Everything is your fault.
I agree with the content of the article, but you're right -- users don't wanna hear it.
Why do you care? Do you think this helps your customer at all? Perhaps you're worried about your technical reputation. All you're doing is moving the blame to some part of your code to the decision you made to host on Heroku. Down is down. Unavailable is unavailable. To your customers that's all that matters. For what it's worth I think hosting on Heroku makes plenty of sense and I'm actually moving my app (Crisply)…
In my experience, users actually do care quite a bit. Back when my company was on Rackspace, we had several periods of significant downtime that weren't our fault. Customers who contacted us were very upset, but when we made it clear that it wasn't a bug with our software, but rather a problem with the hosting provider, they all calmed down. I believe there are at least a few key things a customer takes away from a m…
Why do you care? Do you think this helps your customer at all? Perhaps you're worried about your technical reputation. All you're doing is moving the blame to some part of your code to the decision you made to host on Heroku. Down is down. Unavailable is unavailable. To your customers that's all that matters. For what it's worth I think hosting on Heroku makes plenty of sense and I'm actually moving my app (Crisply)…
When you know it's Heroku, you can deliver valuable uptime to your customers faster because you don't have to spend time testing for bugs and checking server logs--jumping straight to what you would do: contacting Heroku.
Your customers won't be just as screwed--3 hours of down is not the same as 6 hours of down.
Bullshit. It's your fault. I'm your user, you took my money. We're done here. Everything is your fault.
Continue in that vein, then if there is a natural disaster then it is their fault as well. The information is useful. Heroku should provide it. We're done here.
Bullshit. It's your fault. I'm your user, you took my money. We're done here. Everything is your fault.
Continue in that vein, then if there is a natural disaster then it is their fault as well. The information is useful. Heroku should provide it. We're done here.
I speak as someone who's worked primarily in healthcare building services where I assure you we held ourselves personally responsible for natural disasters.
So it depends on your app. If my startup lets people take photos of their dessert and paste lolcats on them, then maybe my hosting goes down and I show my users a page that says the server must have farted, who cares.. but the last thing I'd do is show a page that said the people I pay with their money must be fucking up at the moment and we'll all wait together for things to get better.
Point is: My users are not my peers, they're my responsibility and livelihood. Even when something totally out of my control occurs. Fuck, especially when something out of my control occurs.
Bullshit. It's your fault. I'm your user, you took my money. We're done here. Everything is your fault.