|
|
|
|
|
|
by gingerlime
4824 days ago
|
|
|
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... |
|
|
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.