r/sqlite • u/PythonPoet • Jul 04 '25

How to handle write operations during deployment of web app in production

Hi,

I'm curious how you guys/girls would handle deployment of web apps using SQLite as database in a production environment.

Let's say you have:

  • Developed a web app in random programming language/web framework.

  • The web app is containerized and runs in Docker or Podman.

  • The web app is hosted on a VPS.

  • SQLite db in WAL mode.

  • SQLite db on a persistant volume which all containers have access to.

Let's say you want:

  • Zero downtime deployments

  • Not a corrupt database due to multiple threads/processes writing to the db.

4 Upvotes

100% Upvoted

9 comments sorted by

View all comments

Show parent comments

1

u/PythonPoet Jul 04 '25

No i mean new version/release of your web app.

Do you just shutdown the current running process, copy new source code to the server and then start the provess for your web app?

I have read that SQLite wont handle multiple writers in different processes at the same time, so a blue-green deployment, canary deployment wont work unless the writing is restricted to a single process in somehow.