pgweb VS rqlite

Built Pgweb (Postgres GUI) some time ago since I could not find a good minimalistic database explorer.

https://github.com/sosedoff/pgweb

The app is super simple, made with Go + jQuery and I still use it almost every day, and has brought it to every single company I've been with.

For postgresql, pgweb is perfect.

rqlite[1] could basically do this, if you use read-only nodes[2]. But it's not quite a drop-in replacement for SQLite at the write-side. But from point of view of a clients at the edge, they see a SQLite database being updated which they can directly read[3].

That said, it may not be practical to have hundreds of read-only nodes, but for moderate-size needs, should work fine..

Disclaimer: I'm the creator of rqlite.

[1] https://rqlite.io/

[2] https://rqlite.io/docs/clustering/read-only-nodes/

[3] https://rqlite.io/docs/guides/direct-access/

Not particularly. A C compiler is only needed for the SQLite source code.

I originally provided these musl-based builds so I could provide rqlite Docker images based on Alpine[1]. But now the Docker release process simply builds rqlite from the source during the image-creation process[2].

[1] https://hub.docker.com/_/alpine

[2] https://github.com/rqlite/rqlite/blob/master/Dockerfile

Not Jepsen tested but I'd like rqlite [0] would be in the running and meet the requirements.

0. https://rqlite.io/

I’ve been pondering doing something like this with SQLite. The primary db is local/embedded on the user’s machine and use something like https://github.com/rqlite/rqlite to sync on the backend.

It also means it would be fairly trivial to allow users/orgs to host their own “backend” as well.

SQLite is not competing with RDMBSes. SQLite is competing with fopen().

There are of course solutions which wrap this fopen() replacement in a network/cluster-aware tools, e.g. https://github.com/rqlite/rqlite - these are competing with postgres.

Seems like you could do the same with rqlite [1], since SQLite supports JSON.

[1]: https://rqlite.io