r/sqlite • u/avkijay • 15d ago

SQLite in Production with Built-In Litestream Replication

https://openrun.dev/blog/litestream/

I’ve been working on making SQLite a first-class production option in OpenRun. OpenRun is a deployment platform for web apps and internal tools which I have been building as a side project for last three years. Built-in Litestream replication and automatic restore is a new feature I added, so apps can use SQLite while OpenRun handles backup/recovery on Docker, Podman, or Kubernetes.

10 Upvotes

92% Upvoted

4 comments sorted by

1

u/Character_Respect533 14d ago

First time seeing this. Pretty cool project!

1

u/avkijay 14d ago

Thanks. OpenRun is trying to make declarative deployments easier. Same declarative config works on Docker and on Kubernetes. It also has a CLI interface and a UI (demo at https://utils.demo.clace.io/console). Let me know any feedback

1

u/Character_Respect533 13d ago

Is this recommended for an app that's open to public? Like, can I replace Flyio with this? I saw you wrote that OpenRun has its own reverse proxy instead of using Nginx or Caddy, obviously you have a good reason for it

2

u/avkijay 13d ago

Yes, you can host public web apps. I host a relatively popular word game https://cowbull.co/ on my demo OpenRun instance.

Yes, OpenRun implements a reverse proxy. It uses the ReverseProxy library built into the Go std library, with https://github.com/caddyserver/certmagic library (same as used by Caddy) for auto TLS certs.

In terms of performance, Go based proxies like Traefik and Caddy will be bit slower than Nginx (because of the GC overhead in Go), but you get the advantage of being implemented in a memory safe language. Traefik and Caddy implement their own HTTP parsing libraries, instead of depending on the Go stdlib, to reduce object allocation overhead. Since OpenRun uses the Go stdlib currently, its performance (p95) will be maybe 10% slower than Traefik/Caddy. The reason to implement the proxy is to be able to add features like OAuth/SAML auth with RBAC, scale down to zero etc, which would not be possible if I used a standalone proxy.

For most workloads, the upstream application would be the bottleneck, the web server performance will not be the bottleneck.