> I also think that "my site is free as in beer and also lightning fast" generally transposes to "my site doesn't have any traffic" its more about being able t

> I also think that "my site is free as in beer and also lightning fast" generally transposes to "my site doesn't have any traffic" its more about being able to handle spurts of traffic and sustained traffic. these services are good enough to power whole communities and mobile apps. and that means it covers most use cases, as well as the placeholder websites that may launch a product once. and by most use cases, we're talking about just the 99th percentile of high load intertwined ratsnest products not being able to handle it, but even then that's only because of an insanely high traffic load that is loading unique queries that are impossible to cache and this breaks view rendering - aka the bottleneck is still elsewhere. with things that render quickly and have that view cached on the nearest CDNs, and that have giant memcaches of the queries that will be used, you really aren't needed! fortunately there are many web services that are not designed that way, cannot be designed that way, but more so can't/won't be redesigned that way.