|
|
|
|
|
|
by res0nat0r
4851 days ago
|
|
|
The same can be said for EC2. "Amazon EC2 reduces the time required to obtain and boot new server instances to minutes, allowing you to quickly scale capacity, both up and down, as your computing requirements change." If my instances don't launch "quickly" or I've designed my app in such a way that it isn't 100% linery scalable I can now sue Amazon? You can't sue heroku for their marketing speak. |
|
|
You can sue anyone for anything, success is not assured.
That bit of pedantry aside, Heroku led people on to believe that their queueing backend was intelligently distributing requests to nodes. Rather than randomly.
You are not allowed to argue this, as Heroku themselves acknowledged it!
Furthermore, they blatantly lied about it. From the rap genius article:
Heroku claims that though they received reports of unexplained latency over the past couple of years, they weren’t able to figure out the request queuing issue until they read the Rap Genius article. But there is evidence that Heroku knew about the problem for more than 2 years.
And the conclusion, also from the same article:
Based on Heroku's response so far, it appears their approach to fixing the problem is, “We promised you intelligent routing, we delivered random routing (which is worse than intelligent routing), so we're going to change our documentation to make it clear that we're only promising you random routing.”
This works for future customers, since once Heroku makes these documentation changes, everyone who signs up will understand exactly how routing works. But it does nothing to address the time and money that existing customers have spent over the past few years. What does Heroku owe them?