Database for single payer?

Question

linux

I don't know how to make the title clearer.
I need a database that won't crash when it crashes. Specifically, I need this database to work on my single-board device, which can be turned off at any time by simply pulling it out of the socket. It's not scary if the current operation fails, the main thing is that the database is not damaged.
UPD. I'll try everything that was suggested here, except for writing to a file, since there are quite a lot of records in tables, as well as search operations on them. After a while, I will write where I stopped and note the working options as a solution.

Answer 1

But do not believe it - redis !!! Writes every 15 minutes, recovers, works in memory.

Answer 2

sqlite only write in 1 thread

Answer 3

Write to files, do sync after each write

Answer 4

In fact, all modern DBMSs are designed specifically for this. Ideally, the data should be located not in the file system, but in an unformatted partition, otherwise not all file systems can withstand a power outage.

Answer 5

So it's not a single-payer and not a process. The point is the disk subsystem, how it is organized.