Scaling SQLite to 4M QPS on a Single Server (EC2 vs. Bare Metal)
In this technical retrospective (2020), @fforflo 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 ★ 4 points
TOTAL DISCUSSIONS 1 comments
Colocation seems to have fallen out of favour over the past decade, but it still provides the most bang per buck for server performance. The only difference is that provisioning takes weeks to months vs seconds to minutes via an API call.
Where this has the most impact on performance and cost is visible in storage systems. Low tier solutions on AWS have notoriously bad storage performance. 20MB/s is useless for just about anything modern.