News for hackers. Stuff that matters.
Re:Tailscale Traces Database Corruption to 16y/o SQLite WAL-... by inigyou on Wednesday August 12, 2026 @08:11PM (#49280260)
okay but explain why you are using sqlite and copying the file to S3 instead of using any client/server DB and its online backup feature?
Re:Tailscale Traces Database Corruption to 16y/o SQLite WAL-... by zbentley on Wednesday August 12, 2026 @11:57PM (#49281643)
I don’t think that’s an architectural solution to this class of bug. I replied to a similar comment here: https://news.ycombinator.com/item?id=49281533
Re:Tailscale Traces Database Corruption to 16y/o SQLite WAL-... by raggi on Thursday August 13, 2026 @10:35AM (#49286616)
SQLite has an online backup API as well, but it is slower and requires a significant additional page cache cost.

The team chose SQLite early on (there are some blog posts about this) and then we vertically scaled against the SQLite architecture. There are subtle ways you come to depend on the proximity/latency when you scale with local storage that mean switching requires a lot of non-obvious work - it’s probably the largest hazard for embracing SQLite in a growing saas - but at the same time you can push the vertical scale pretty far, which has great margins.

Had we scaled a different architecture of database there’s little reason to believe it would have been plain sailing as seems to be implied here.