100,000 TPS OVER A BILLION ROWS: THE UNREASONABLE EFFECTIVENESS OF SQLITE

Summary from the TLDR Dev newsletter

SQLite's embedded nature and single-writer limitation are usually seen as drawbacks, but are actually important to its scalability. By removing network latency and enabling batching, SQLite can achieve much higher transactions per second (TPS) compared to networked databases like Postgres, especially when dealing with power-law distributed workloads and interactive transactions. This is shown by benchmarks of SQLite reaching over 100,000 TPS even with concurrent reads, while Postgres is much worse with added network latency.