|
|
|
|
|
by goldenkey
4505 days ago
|
|
A little time spent learning how to use a server and build an actual scaling infrastructure, and Heroku turns into dust for dumb dorks. Heroku is the MSFT of servers, lock yourself in, and prepare to feel the bind as it gets tighter. Seriously people, DIY, it isn't hard. Let the "180 websites in 180 days" [1] girl use Heroku, she's giddy to get anything working. Real hackers should not be satisfied with lock-in, ridiculous prices that correlate with the ineptitude of the user-base, potential downtime on top of AWS normal downtime (what Heroku uses in the background.) If you're serious about your business, Heroku makes no sense at all, lest you be a non-technical cofounder, and it makes you feel 'safe.' [1] http://jenniferdewalt.com/ |
|
As to the point of DIY not being hard, getting something working may not be hard. But handling fault tolerance, logging, backup, downtime, etc. is non-trivial. And as mentioned in other comments, this takes time. Even if you're a l33t ub3r h4x0r, that will always be true. For some teams, the DIY investment will make sense, others would rather spend their time building features than dealing with ops.