3 ms·
Heroku has a history of making technical changes that are actually worse performance-wise and reliability-wise. One of the more notable ones was the switch fro
by yellowapple 11y ago
Heroku has a history of making technical changes that are actually worse performance-wise and reliability-wise. One of the more notable ones was the switch from an "intelligent" request routing mechanism (Heroku's routing mesh would route requests to dynos based on their load) to a random load-balancing scheme (blind, with no regard for existing dyno load), causing requests to frequently be routed to overworked dynos while leaving open ones idling and twiddling their virtual thumbs. This change was eventually called out and documented by the folks at Rap Genius [0]; Heroku eventually responded, though I don't know off the top of my head whether they went back to their previous (and arguably much-superior) routing system.
This, combined with the rather abysmal tooling (and, of course, the rather abysmal pricing) around Heroku, left a bad enough taste in my mouth to avoid Heroku for most (if not all) of my personal projects, the sole exception at the moment being heroku-sucks.herokuapp.com. My current dayjob employer (a Rails consultancy) has switched away from Heroku entirely, moving instead to Cloud66 (we haven't gone the container route yet, but we're actively working on it).
[0]: http://genius.com/James-somers-herokus-ugly-secret-annotated http://genius.com/James-somers-herokus-ugly-secret-annotated