Three containers writing to one database

The web container takes orders. The worker container processes them. The reporting container reads them. All three need the same SQLite file. In a normal setup, this is the moment you switch to Postgres.

You don't. You put the file in /hoody/databases/orders.db and all three containers open it. The path is a special FUSE mount that coordinates writes across containers: no database is locked errors, no corruption, no extra config. Each container thinks it's writing to a local file. The host knows otherwise.

You keep your zero-driver, single-binary, copy-the-file-to-back-it-up SQLite simplicity. You also get the multi-process behavior you'd normally pay a Postgres tax for.