SQLite Is a Library of Congress Recommended Storage Format

Original Article ↗ Hacker News Discussion ↗

LoC recommendation and archival use

  • SQLite is praised as a strong choice for public‑sector and long‑term preservation:
    • Open, well‑documented spec, widely adopted, low patent risk.
    • Single-file format preserves relational structure in ways CSV cannot.
    • Seen as likely to remain readable for centuries, aligning with archivists’ long‑term thinking.
  • LoC’s broader 2026 guidance prefers platform‑independent text formats, SQLite‑style .db files, and even some proprietary de‑facto standards like XLS/XLSX, which some find surprisingly “lax.”

Corporate/security and governance concerns

  • Some firms reportedly ban SQLite:
    • Because a critical database “looks like a file,” can have any extension, and be trivially copied with embedded PII.
    • Centralized DB servers are seen as easier to control, audit, and wrap with enterprise processes.
  • Others mock this stance, pointing out that Excel, text files, and even “brains” routinely become shadow databases.
  • Several mention governance approaches: classification rules, storage policies, and PII scanners on Office documents.

Excel, Access, and shadow databases

  • Many note Excel is heavily misused as a database:
    • It approximates tables, keys, and even rudimentary forms, so it becomes a de‑facto DB.
    • Some organizations restrict what can go in spreadsheets and where they are stored.
  • Access is widely criticized for corruption and poor suitability as a shared DB.
  • Some argue companies that ban SQLite but allow Excel are being inconsistent.

Reliability, performance, and use cases

  • Multiple commenters report excellent reliability using SQLite for most apps, especially in “single writer, many readers” patterns with WAL and basic tuning.
  • Others mention data loss or corruption experiences and say that was enough to stop using it; countered by reminders that backups are necessary for any medium.
  • SQLite’s simplicity (binary + file) is popular for small to medium apps; some wish for SQLite‑like systems with higher concurrent write throughput.
  • Extensions and patterns (e.g., sharding with ATTACH, WAL tuning, pub/sub extensions) are cited as expanding SQLite’s applicability.

Filesystems and portability

  • One commenter describes switching to SQLite on exFAT to avoid inventing ad‑hoc journaling, highlighting SQLite as a way to get ACID semantics atop weak filesystems.
  • Broader debate on the lack of a single, robust, universally supported filesystem; exFAT is seen as a lowest‑common‑denominator despite serious drawbacks.