3 ms·
Serving static HTTP GETs is easy. The moment you start trying to make money off the generated traffic its no longer a read only affair. Your system is not state
by speed_spread 5y ago
Serving static HTTP GETs is easy. The moment you start trying to make money off the generated traffic its no longer a read only affair. Your system is not stateless anymore and tracking costs spiral up quickly.
- marginalia_nu 5y agoI largely agree with the analysis, with the caveat that a search engine is a bit more involved than serving static GETs.
- speed_spread 5y agoSorry, I lost context and was not thinking of the search engine but of a statically generated blog with small pages and little media. Also, thanks for confirming my hunch about the bigger factor being statefulness rather than dynamicity. CPU, RAM storage are incredibly cheap nowadays. But so much can be going on at a time that _certainty_ is now what's pricey.