<story><title>Ask HN: How does HN manage to be always online?</title><text>How does HN manage to be always online?</text></story><parent_chain></parent_chain><comment><author>5id</author><text>According to @dang (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=28479595&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=28479595&lt;/a&gt;) via @sctb (&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=16076041&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=16076041&lt;/a&gt;)&lt;p&gt;&lt;pre&gt;&lt;code&gt;  We’re recently running two machines (master and standby) at M5 Hosting. All of HN runs on a single box, nothing exotic:
  CPU: Intel(R) Xeon(R) CPU E5-2637 v4 @ 3.50GHz (3500.07-MHz K8-class CPU)
  FreeBSD&amp;#x2F;SMP: 2 package(s) x 4 core(s) x 2 hardware threads
  Mirrored SSDs for data, mirrored magnetic for logs (UFS)&lt;/code&gt;&lt;/pre&gt;</text></comment>
<story><title>Ask HN: How does HN manage to be always online?</title><text>How does HN manage to be always online?</text></story><parent_chain></parent_chain><comment><author>nik736</author><text>A single bare metal server is more reliable than most people think it is. Complexity adds a lot of overhead and layer after layer that could possibly fail.</text></comment>