The definitive guide to using Django with SQLite in production 💡

1. litestream

   1 192 12,967 9.1 Go

   Streaming replication for SQLite.

   

   ... # Install wget and Litestream RUN --mount=type=cache,target=/var/cache/apt,sharing=locked --mount=type=cache,target=/var/lib/apt,sharing=locked \ apt-get update --fix-missing && \ apt-get install --no-install-recommends -y wget && \ wget https://github.com/benbjohnson/litestream/releases/download/v0.3.13/litestream-v0.3.13-linux-amd64.deb && \ dpkg -i litestream-v0.3.13-linux-amd64.deb ENTRYPOINT ["./entrypoint.sh"]

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. litestack

   2 24 1,442 8.0 Ruby

   

   There has been a lot of conversation about using SQLite as a production database for websites for the past few years, espeically in the Rails community with Litestack. And now, in the latest version of Rails, SQLite has become the defacto backend for many parts of the stack.

4. sqlite

   3 27 122 10.0 C

   sqlite mirror (by smparkes)

   

   I currently have a managed PostgreSQL database at Digital Ocean which has worked well, but I have been looking into using SQLite in production to reduce server costs and network latency. And, since I'm not particularly DevOps-y, I do not want to be on the hook for maintaining my own PostgreSQL database. So, I have been investigating other solutions for my newest side project, filmcliq.com.

5. django_libsql

   4 1 3 - Python

   Discontinued [GET https://api.github.com/repos/profusion/django_libsql: 404 - Not Found // See: https://docs.github.com/rest/repos/repos#get-a-repository]

   

   Turso libSQL: A fork of SQLite that supports distributed databases (django-libsql)

6. libsql

   5 38 15,960 9.6 C

   libSQL is a fork of SQLite that is both Open Source, and Open Contributions.

   

   Turso libSQL: A fork of SQLite that supports distributed databases (django-libsql)

7. marmot

   6 37 2,088 6.5 Go

   A distributed SQLite replicator built on top of NATS

   

   marmot: A distributed SQLite replicator built on top of NATS

8. rqlite

   7 131 17,174 9.8 Go

   The lightweight, fault-tolerant database built on SQLite. Designed to keep your data highly available with minimal effort.

   

   rqlite: The lightweight, user-friendly, distributed relational database built on SQLite

9. Stream

   getstream.io featured

   Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.

   

10. django-q2

    8 3 559 5.3 Python

    A multiprocessing distributed task queue for Django. Django Q2 is a fork of Django Q. Big thanks to Ilan Steemers for starting this project. Unfortunately, development has stalled since June 2021. Django Q2 is the new updated version of Django Q, with dependencies updates, docs updates and several bug fixes. Original repository: https://github.com/Koed00/django-q

    

    django-q2

11. django-db-queue

    9 6 182 6.7 Python

    Simple database-backed job queue

    

    django-db-queue

12. huey

    10 15 5,829 6.4 Python

    a little task queue for python

    

    huey

13. blaze-starter

    11 2 44 7.9 Shell

    Discontinued Blaze.horse — Django Starter Kit

    

    blaze-starter start.sh

14. coolify

    12 169 48,593 10.0 PHP

    An open-source, self-hostable PaaS alternative to Vercel, Heroku & Netlify that lets you easily deploy static sites, databases, full-stack applications and 280+ one-click services on your own servers.

    

    I have been running Django sites in production under heavy load for over 10 years at my day job. We started with a MySQL database backend but, after running into a few issues, switched to PostgreSQL which has been rock-solid. I tend to use the same stack for side projects. Especially because, initially, most of my projects were hosted on Heroku and they had stellar support for PostgreSQL. Now, having bounced from Heroku to Render to Fly.io to Digital Ocean (with CapRover) to Hetzner (with Coolify), I am re-evaluating my default choice of database.

Suggest a related project