faenz VS dqlite

Two years back, I created a little web analytics tool for my side projects and I called Faenz. It's open source and self-hostable, available on GitHub at https://github.com/a-chris/faenz.

I've recently given it an update and came up with the idea of creating a demo version that's accessible to everyone.

How does it work?

You can add your own website, blog or e-commerce site and keep track of the visits it receives. Your website stats will be visible to others, and you'll get to check out everyone else's stats too. You won't be allowed to edit/delete a website, you should reach out to me for that.

I find it to be a fun experiment to see how people handle SEO or just to discover some cool new websites :)

The demo is available here https://faenz.acmecorp.dev/

Here is the project I'm working on: Faenz Analytics

I've built several personal projects to be honest; background jobs, tasks automation, telegram bots to find a house to rent or buy, most of them are kept provate.

The two I'm most proud of are a web analytics that, coincidentally, I've made public today after a few weeks of work:

https://github.com/a-chris/faenz

I developed it for collect data for my personal website and it is working well so far, really happy of it.

The other one is a Google Chrome extension to manage bookmark because I think the default one is a mess and very unpratical to use. I haven't worked on it for a while:

https://github.com/a-chris/peffect-bookmarks-manager

If you're interested in this, here are some related projects that all take slightly different approaches:

- LiteSync directly competes with Marmot and supports DDL sync, but is closed source commercial (similar to SQLite EE): https://litesync.io

- dqlite is Canonical's distributed SQLite that depends on c-raft and kernel-level async I/O: https://dqlite.io

- cr-sqlite is a Rust-based loadable extension that adds CRDT changeset generation and reconciliation to SQLite: https://github.com/vlcn-io/cr-sqlite

Slightly related but not really (no multi writer, no C-level SQLite API or other restrictions):

- comdb2 (Bloombergs multi-homed RDMS using SQLite as the frontend)

- rqlite: RDMS with HTTP API and SQLite as the storage engine, used for replication and strong consistency (does not scale writes)

- litestream/LiteFS: disaster recovery replication

- liteserver: active read-only replication (predecessor of LiteSync)

I'd be curious for a similar tuning with Dqlite: https://github.com/canonical/dqlite

Anyone knows how the DB this is about, https://rqlite.io/, compares with https://dqlite.io/ by Canonical (both seem to be distributed versions of sqlite)?

For folks' context, the new tool that's being discussed in the thread mentioned by the parent here is litefs [0], as well as which you can also look at rqlite [1] and dqlite [2], which all provide different trade-offs (e.g. rqlite is 'more strongly consistent' than litefs).

[0]: https://github.com/superfly/litefs

[1]: https://github.com/rqlite/rqlite

[2]: https://github.com/canonical/dqlite

I presume you're familiar with https://github.com/canonical/dqlite (made by my employer) and https://github.com/rqlite/rqlite (unrelated)? How will mvsqlite compare to those?

Check out dqlite, it's sqlite but with a raft consensus to distribute changes through a log: https://dqlite.io/ You can link it in as a library too, it sounds like exactly what you want.