Unsurprisingly, comments start pointing the way to added complexity like Postgres and containers and whatnot, but this is exactly the right approach for probabl

Unsurprisingly, comments start pointing the way to added complexity like Postgres and containers and whatnot, but this is exactly the right approach for probably the large majority of webapps out there. One executable, one db-file, up and running anywhere within a very few minutes. With a modicum of intelligence thrown into the design, you're never ever going to see SQLite acting bottleneck. Few sites have request rates on the scale of tens of thousands per second. Developers of would-be federated services to decentralize the web, please take note. This is how you go about ensuring wide deployment. Simplicity, if anyone remembers the word.