Did you read the article past the benchmark numbers? That's more-or-less exactly the point the author made by the end. To wit: > The majority of web applicatio

Did you read the article past the benchmark numbers? That's more-or-less exactly the point the author made by the end. To wit: > The majority of web applications handle far less than 1000 requests per second. I’d go as far as to say that most web application developers are employed by a company whose entire webapp does far less than 1000 requests/second. Most of them do less than 1000 requests/minute. > When your application is big enough to be doing 20,000 RPM, you will have anywhere from a half-dozen to even fifty engineers, depending on your application’s domain. A single software engineer costs a company at least $10,000/month in employee benefits and salary. So we’re choosing our frameworks based on saving one-third of an engineer per month? And if that framework caused your development cycles to slow down by even one third of a mythical man-month, you’ve increased your costs, not decreased them. Choosing a web framework based on server costs is clearly a sucker’s game. > What does web-scale even mean? It's an old-ish meme, from this video making fun of MongoDB. [1] 1: https://www.youtube.com/watch?v=b2F-DItXtZs https://www.youtube.com/watch?v=b2F-DItXtZs