Scaling SQLite to 4M QPS on a Single Server
In this technical retrospective (2021), @exec shares practical architectural lessons learned from running, scaling, or migrating production software under lean constraints.
Core Principles for Independent Builders:
Defaulting to simpler architectures (such as monolithic frameworks, SQLite, or managed VPS) prevents early engineering bankruptcy.
Evaluating true compute and egress costs reveals that high cloud bills can often be slashed by 80%+ through judicious re-platforming.
Code you write at 2 AM as a solo engineer must be easy to debug six months later without complex microservice dependencies.
Community Debate Themes:
HN engineers debated the tradeoffs between cloud convenience and raw server economics, database indexing strategies, and resisting premature architectural complexity.
CATEGORY Frugal Engineering →
HISTORICAL ERA Pandemic Bubble (2020–2022)
COMMUNITY SCORE ★ 38 points
TOTAL DISCUSSIONS 4 comments
The epilogue mentions meltdown and spectre. I’m no expert on these, but wouldn’t the use case of a self hosted server where you install trusted applications only not be affected by meltdown and spectre?
My understanding was the w biggest worries with those bugs were precisely in the cloud, since they run untrusted code and run multiple users on the same hardware.
What does making RANDOM() deterministic mean? Seems like it defeats the purpose of generating randomness.
This is from 2018, but still interesting.