I wondered whether this comparison (like many others like it) would /finally/ bake cluster operational costs into the calculus. Not this time, it looks like. T

I wondered whether this comparison (like many others like it) would /finally/ bake cluster operational costs into the calculus. Not this time, it looks like. To raise a more constructive point. Looking at [1] (an earlier post in the series), it looks like their workload is WordPress + VBulletin forums, and "pets" not "cattle" -- I wonder how much more they'd be able to get from separating their stateful and stateless layers more cleanly, and using some of the more powerful (and cheaper) AWS primitives for serving traffic that involves the latter. Why do they need such beefy instances for essentially serving content? The truth is, it's because the platforms they're using (vBulletin + WP) exist, they're very powerful and they get the job done. This leads me to believe that the operational UX for running these kinds of common applications (which compose most of the internet) on AWS without highly technical supervision is not great. [1] https://www.servethehome.com/falling-sky-part-3-evaluating-amazon-ec2-vps-dedicated-colocation-options/ https://www.servethehome.com/falling-sky-part-3-evaluating-a...