Hacker News Reader

Comment by ramraj07 | Hacker News Reader

Wait , are you running this site on a raspberry pi?

The biggest issue with SQLite is what happens if your server serving stuff goes down mid write? Power surge maybe. You lose data from that day till previous cronjob?

View on HN

> The biggest issue with SQLite is what happens if your server serving stuff goes down mid write?

Why would that matter? SQLite is still fully ACID compliant like other DBs.

I imagine that GP means a hardware failure severe enough that it permanently borks the disk drive of the machine. In that case vanilla SQLite would indeed lose data written since the time of the last offsite backup. MySQL/Postgres/etc typically have streaming replication which means you can promote one of the replicas and not lose any (or at least much less) data. There are some new-ish projects like Litestream (https://litestream.io/) that provide a similar functionality for SQLite by streaming the WAL file changes to S3.

The "boots up our application within a second on a Raspberry Pi" comment in the FAQ[0] is actually about my development setup, as I don't own a fancy computer myself. It was mainly meant to illustrate the fast startup time of the Janet[1] language. In fact, that startup time is so fast, you can run your app as a CGI script. That has some more possible advantages, see the FAQ for more details.

[0] FAQ: https://withoutdistractions.com/cv/faq#technology

[1] Janet: https://janet-lang.org/

They do gain some data security as they've effectively sharded their database by user. So at the point of a power failure only the active users' data would be at risk of corruption at the file level.

Of course there's always the risk of damage to the media in general, but then you can never fully protect against hardware failures.

Reply on news.ycombinator.com