6 ms·

I thought your stack was mostly go?

• kasey_junk 11y ago
  I suspect that was irony...
  • mwcampbell 11y ago
    In a blog post some months ago [1], Patrick said that some components do use Rails. [1] http://www.kalzumeus.com/2015/08/20/designing-and-building-stockfighter-our-programming-game/ http://www.kalzumeus.com/2015/08/20/designing-and-building-s...
    • joshmn 11y ago
      I know using Rails isn't as popular here as it once was, but in my experience, if you cache correctly (like you should), it's trivial to scale.
      • patio11 11y ago
        Modestly less trivial if you happen to put your chat server on the box with Rails because Rails is certainly not going to fall over and your chat server attempts to open several thousand websockets on a box with a not-too-generous number of open file descriptors, it appears.
        • jerf 11y ago
          "Make sure you've turned up the file descriptors" is the single-process socket server equivalent of "Turn off HTTP KeepAlive" for Apache sites. :) (Yeah, I've had outage because of this too.)
          • ehsanu1 11y ago
            Surely you meant "Turn on HTTP pipelining"? Or is there something wrong with Apache's pipelining implementation?
            • MichaelGG 11y ago
              As I understand, HTTP pipelining is basically a no-go in the real world. Broken implementations, plus performance implications since responses must go in order. Edit: Here's a FF discussion on it: https://bugzilla.mozilla.org/show_bug.cgi?id=264354 https://bugzilla.mozilla.org/show_bug.cgi?id=264354 -
            • jerf 11y ago
              I misremembered a bit; it was Turn Off Apache Keepalive: https://hn.algolia.com/?query=patio11%20apache%20keepalive&sort=byPopularity&prefix&page=0&dateRange=all&type=comment https://hn.algolia.com/?query=patio11%20apache%20keepalive&s...
        • mbesto 11y ago
          I feel like a chat server is something best served by something not in your stack (especially Rails). I surprised you chose to do it in house. How about using https://pusher.com/ https://pusher.com/ or https://www.firebase.com/ https://www.firebase.com/ ?
          • wglb 11y ago
            Perhaps those lack useful vulnerabilities?
          • deleted 11y ago
            [deleted]
        • dchuk 11y ago
          Why in this day and age of cheap and easy servers would you ever have more than one service type running on a server in production? It's trivial to break things up nowadays
  • lopatin 11y ago
    Looks like it's actually Go based on one of the JSON responses I found in the web page: { ok: false, error: "strconv.ParseInt: parsing "NaN": invalid syntax" }
• tptacek 11y ago
  It's mostly Go except where it isn't.
• gjm11 11y ago
  It currently appears to be mostly stop.