[ryan_f]

This is rather disconcerting. They are given us a window of 48 hours where our site will be down for 60 seconds. On top of that we cannot schedule the time with them.

60 seconds may seem like a small inconvenience but it is one still the same. I host a few clients on their servers and I need to relay this information. I sound like a jackass being that I can't give more specifics on the timing of the server being down to my clients. How does Heroku not feel the same?

I am appreciative of the update but that is also what I pay them to do.

[fein]

> How does Heroku not feel the same?

Because they, as a hosting provider, have several orders of magnitude more clients to please than yourself. The only way to be fair to everyone is that everyone gets treated like shit (obviously embellished).

All you should be doing to CYA is telling your clients exactly why this is happening and that its Heroku, and not you, that holds the blame at this point.

The caveat would be those difficult customers (suits, exec managers, etc) that you have to handle with kid gloves. For these people... I don't think there's a graceful way to present the upcoming issue.

[gingerlime]

I doubt customers typically know or care whether you use heroku, Amazon or any other provider. What they want is to see their system up and running.

That said, I wonder if with the heroku postgresql setup, this vulnerability could mean that if even one db is compromised, it could allow access to other databases too. Maybe heroku runs several postgresql db's on the same virtual/physical hosts?. If that's the case, then heroku simply can't afford to let even one database stay exposed because it would risk all others.

Whether or not this is the case, I don't know, but it kinda feels like running your app on a shared-hosting account...

[lambda]

> Whether or not this is the case, I don't know, but it kinda feels like running your app on a shared-hosting account...

Remember that you are running your app on a shared hosting account with Heroku.

Now, it has somewhat more isolation than a typical shared hosting account, but less isolation than using physically separate hardware.

Heroku is built on top of AWS, so your machine is running on the same physical hardware, though a different virtual machine, as other AWS customers. Furthermore, Heroku uses LXC to isolate its dynos; so you are running on the same VM as another Heroku customers, albeit separated by a container barrier. And finally, if you're using Postgres, then you're running on a shared database service, which is pretty much exactly like what you'd get with shared hosting.

[criley]

>What they want is to see their system up and running.

This would be a good chance to take a step back and think about what's more important: using Heroku or controlling your up-time?

[ryan_f]

I understand they have more clients to please than myself. Even a smaller window of time would be helpful or to know it is going to be done in off hours. There's no reason I should be fine with this as a paying customer.

[arielserafini]

I don't think a company that has clients all around the globe like Heroku has "off hours".