Backup Strategies for SQLite in Production
In this technical retrospective (2024), @mpweiher 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 Post-ZIRP & AI (2023–2026)
COMMUNITY SCORE ★ 37 points
TOTAL DISCUSSIONS 3 comments
The article is a bit convoluted. The parts about the "if remote target" is unnecessarily repeated. The most recommended backup strategy is 3-2-1, regardless of what you want to backup. You could have explained that in the beginning and then just compared the different backup strategies -- cp, sqlite backup api, dumps -- and their advantages and disadvantages.