dqlite VS boringproxy

Compare dqlite vs boringproxy and see what are their differences.


Embeddable, replicated and fault tolerant SQL engine. (by canonical)


Simple tunneling reverse proxy with a fast web UI and auto HTTPS. Designed for self-hosters. (by boringproxy)
Our great sponsors
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
  • SonarLint - Clean code begins in your IDE with SonarLint
  • Mergify - Updating dependencies is time-consuming.
dqlite boringproxy
32 9
3,538 916
1.7% 3.5%
0.0 0.0
8 days ago 3 months ago
C Go
GNU General Public License v3.0 or later MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of dqlite. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-22.


Posts with mentions or reviews of boringproxy. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-05.
  • Replacing cloudflare with a VPS - My journey
    3 projects | /r/selfhosted | 5 May 2023
    Finally, someone in the above project's Matrix room directed me towards boringproxy - https://github.com/boringproxy/boringproxy. This was the perfect solution. No lengthy config files, easy to use and automate. Setup took about an hour and now everything is back up and running. The only issue I've currently not been able to solve is one where the container seems to use a websocket, which keeps getting timed out (will investigate this further tomorrow).
  • zrok: open-source peer-to-peer sharing (alternative to ngrok)
    2 projects | /r/opensource | 8 Mar 2023
    boringproxy (GitHub) is my go-to for this sort of thing. Thanks for the announcement, I'll have to do a head-to-head and see how they stack up!
  • Consider SQLite
    13 projects | news.ycombinator.com | 29 Dec 2021
    Am I the only one who thinks SQLite is still too complicated for many programs? Maybe it's just the particular type of software I normally work on, which tends towards small, self-hosted networking services[0] that would often have a single user, or maybe federated with <100 users. These programs need a small amount of state for things like tokens, users accounts, and maybe a bit of domain-specific things. This can all live in memory, but needs to be persisted to disk on writes. I've reached for SQLite several times, and always come back to just keeping a struct of hashmaps[1] in memory and dumping JSON to disk. It's worked great for my needs.

    Now obviously if I wanted to scale up, at some point you would have too many users to fit in memory. But do programs at that scale actually need to exist? Why can't everyone be on a federated server with state that fits in memory/JSON? I guess that's more of a philosophical question about big tech. But I think it's interesting that most of our tech stack choices are driven by projects designed to work at a scale most of us will never need, and maybe nobody needs.

    [0]: https://boringproxy.io/

    [1]: https://github.com/boringproxy/boringproxy/blob/master/datab...

  • Architecture issue with running a docker project - have a crack at this
    2 projects | /r/docker | 31 Mar 2021
    Hi, so I'm trying to build a project using Docker: (https://github.com/boringproxy/boringproxy) but I can't get it to run because I get this error: root@ubuntu:~/boringproxy# docker-compose up Recreating boringproxy_boringproxy_1 ... done Attaching to boringproxy_boringproxy_1 boringproxy_1 | standard_init_linux.go:219: exec user process caused: exec format error boringproxy_boringproxy_1 exited with code 1 Everything seems to build fine but it just won't execute on docker-compose up. I know the error above is an architectural issue, e.g. building an arm64 image and running it on amd64 but I can't work out why it's building for another arch. I was looking around and commit ada81bae62 actually worked for me, but obviously it doesn't have the most up-to date source code. I did browse the files in the commit and I can't see any changes that absolutely jump out at me; I have no experience of Docker and I've used several different distributions and architectures (arm64, amd64 etc) but nothing works. If someone with even slightly more experience with Docker could have a look at this, I'd appreciate it!
    2 projects | /r/docker | 31 Mar 2021
    This is the commit that seems to have broken the docker image.

What are some alternatives?

When comparing dqlite and boringproxy you can also consider the following projects:

rqlite - The lightweight, distributed relational database built on SQLite

kine - Run Kubernetes on MySQL, Postgres, sqlite, dqlite, not etcd.

litestream - Streaming replication for SQLite.

better-sqlite3 - The fastest and simplest library for SQLite3 in Node.js.

Gravitational Teleport - Protect access to all of your infrastructure.

Bedrock - Rock solid distributed database specializing in active/active automatic failover and WAN replication

mvsqlite - Distributed, MVCC SQLite that runs on FoundationDB.

SQLite - Official Git mirror of the SQLite source tree

litefs - FUSE-based file system for replicating SQLite databases across a cluster of machines

edge-sql - Cloudflare Workers providing a SQL API

Olric - Distributed in-memory object store. It can be used both as an embedded Go library and as a language-independent service.

ipfs-cluster - Pinset orchestration for IPFS