<story><title>How to avoid picking the wrong technology just because it&apos;s cool</title><url>https://blog.bradfieldcs.com/you-are-not-google-84912cf44afb</url></story><parent_chain><item><author>aqme28</author><text>&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;engineering.hellofresh.com&amp;#x2F;scaling-hellofresh-api-gateway-7d40be55450f&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;engineering.hellofresh.com&amp;#x2F;scaling-hellofresh-api-ga...&lt;/a&gt;</text></item><item><author>squeaky-clean</author><text>I remember reading a scaling-out article from some startup. Some of the things felt a little over-engineered, some were impressive, some seemed wrong. But then they get to the point where they brag about their scale, and the metric they used was that they can handle thousands of requests.... per day.</text></item><item><author>Animats</author><text>The author&amp;#x27;s acronym is silly, but it&amp;#x27;s a real problem. Soylent liked to blither about their &amp;quot;infrastructure&amp;quot;, for a product that sells a few times per minute. They could be using CGI scripts on a low-end hosting service and it would work fine.&lt;p&gt;Wikipedia is some MySQL databases with read-only slaves front-ended by Ngnix caches and load balancers.  That seems to get the job done.  Wikipedia is the fifth busiest web site in the world.&lt;p&gt;Netflix&amp;#x27;s web site (not the playout system) was originally a bunch of Python programs.&lt;p&gt;The article mentions a PostGres query that required a full table scan.  If you&amp;#x27;re doing many queries that require a full table scan, you&amp;#x27;re doing something wrong. That&amp;#x27;s what indices are for.</text></item></parent_chain><comment><author>tnolet</author><text>This is hilarious and sad at the same time. However, most of these write ups are aimed at attracting talent. Even more, some tech stacks are deliberately built to attract talent when the core domain is just too simple or boring. &amp;quot;We serve user subscriptions and recipe data from an SQL database using Rails&amp;quot; just doesn&amp;#x27;t sound as snappy as the infra-porn on the blog.</text></comment>
<story><title>How to avoid picking the wrong technology just because it&apos;s cool</title><url>https://blog.bradfieldcs.com/you-are-not-google-84912cf44afb</url></story><parent_chain><item><author>aqme28</author><text>&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;engineering.hellofresh.com&amp;#x2F;scaling-hellofresh-api-gateway-7d40be55450f&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;engineering.hellofresh.com&amp;#x2F;scaling-hellofresh-api-ga...&lt;/a&gt;</text></item><item><author>squeaky-clean</author><text>I remember reading a scaling-out article from some startup. Some of the things felt a little over-engineered, some were impressive, some seemed wrong. But then they get to the point where they brag about their scale, and the metric they used was that they can handle thousands of requests.... per day.</text></item><item><author>Animats</author><text>The author&amp;#x27;s acronym is silly, but it&amp;#x27;s a real problem. Soylent liked to blither about their &amp;quot;infrastructure&amp;quot;, for a product that sells a few times per minute. They could be using CGI scripts on a low-end hosting service and it would work fine.&lt;p&gt;Wikipedia is some MySQL databases with read-only slaves front-ended by Ngnix caches and load balancers.  That seems to get the job done.  Wikipedia is the fifth busiest web site in the world.&lt;p&gt;Netflix&amp;#x27;s web site (not the playout system) was originally a bunch of Python programs.&lt;p&gt;The article mentions a PostGres query that required a full table scan.  If you&amp;#x27;re doing many queries that require a full table scan, you&amp;#x27;re doing something wrong. That&amp;#x27;s what indices are for.</text></item></parent_chain><comment><author>x0x0</author><text>ergh, you weren&amp;#x27;t kidding.  I hope that was a typo on their part; even low thousands rpm is mostly not a big deal on modern hardware.&lt;p&gt;&lt;pre&gt;&lt;code&gt;   Our gateway is on the frontline of our infrastructure. It receives thousands 
   of request per day, and for that reason we chose Go when building it, 
   because of its performance, simplicity, and elegant solution to concurrency.&lt;/code&gt;&lt;/pre&gt;</text></comment>