How Heroku Works

by swampthing on 7/17/2013, 3:00 AM with 36 comments
  • by benhalllondon on 7/17/2013, 3:37 AM

    Re: The Rap Genius Question:

    """A random selection algorithm is used for HTTP request load balancing across web dynos""

    bit more....

    """and this routing handles both HTTP and HTTPS traffic. It also supports multiple simultaneous connections, as well as timeout handling."""

  • by davidbanham on 7/17/2013, 4:29 AM

    """"If you’re using some established framework, Heroku can figure it out. For example, in Ruby on Rails, it’s typically rails server, in Django it’s python <app>/manage.py runserver and in Node.js it’s node web.js."""

    Been working in node for years now, have never named anything web.js. Why not index.js, server.js or app.js?

  • by happywolf on 7/17/2013, 8:06 AM

    Not trusting a company that has a record of inaccurate documentations, and a record of ignoring customer complaints until got hammered hard (enough)

  • by positr0n on 7/17/2013, 3:50 AM

        For example, dynos are cycled at least once per day
    Why so often? I wonder if this is just to protect against memory leaks leading to poor performance from poorly coded apps or if it's an issue with their infrastructure.

  • by oelmekki on 7/17/2013, 6:20 AM

    > Terminology: Dynos are isolated, virtualized Unix containers, that provide the environment required to run an application.

    ... also known as "process".

  • by tlrobinson on 7/17/2013, 6:06 AM

    Here's my outsider's analysis of how Heroku works (well, worked in 2011) from a couple years ago: https://www.quora.com/Scalability/How-does-Heroku-work

  • by znowi on 7/17/2013, 6:48 AM

    Since Heroku's Ugly Secret I don't trust this company.

    http://news.rapgenius.com/James-somers-herokus-ugly-secret-l...