Heroku's Ugly Secret: The story of how the cloud-king turned its back on Rails

Re:Heroku's Ugly Secret: The story of how the cloud-king tur... by doktrin on Thursday February 14, 2013 @02:42AM (#5218309)

Thanks for the response, but I have to admit that the lack of a clear-cut answer here is a little worrisome.

Anyone who wants to like Heroku would hope that the OP is flat out, 100%, wrong. The fact that Heroku's official answer requires a bit of managing implies otherwise.

On a related tangent, I would also encourage future public statements to be a little less opaque than some Heroku has put out previously.

For instance, the cause of the outage last year was attributed to "...the streaming API which connects the dyno manifold to the routing mesh" [1]. While that statement is technically decipherable, it's far from clear.

[1] https://status.heroku.com/incidents/372

[ Parent | on HN ]

Re:Heroku's Ugly Secret: The story of how the cloud-king tur... by toyg on Thursday February 14, 2013 @05:03AM (#5218759)

Maybe it doesn't need "managing", Oren might just want to talk with whoever was responsible for the change and see what the best way forward is. I don't think panicked, knee-jerk reactions like "OMG we were wrong and will revert that commit pronto!" are beneficial in situations as complex as this.

[ Parent | on HN ]

Re:Heroku's Ugly Secret: The story of how the cloud-king tur... by doktrin on Thursday February 14, 2013 @05:44AM (#5218855)

You're assuming that the change was actually made. Until we hear definitively from Heroku, the only evidence is an (admittedly, well documented) blog post.

[ Parent | on HN ]

Re:Heroku's Ugly Secret: The story of how the cloud-king tur... by toyg on Thursday February 14, 2013 @08:35AM (#5219346)

Yeah, absolutely. I'm just saying we can't expect a to manager to immediately respond to a highly-technical issue questioning subtle changes in internal behaviour which might have been introduced years ago.

[ Parent | on HN ]