Thanks, that's a great list! Might be worth mentioning our engine there too, for people who want a graph database atop SQLite and other battle-tested relational databases like MySQL, MariaDB, Postgres.
Our database abstraction layer (and optional ORM) has been battle tested in production for millions of users, and has 3 adapters: Sqlite, Postgres, MySQL/MariaDB. And recently it even added vector search for ranking results by similarity: https://github.com/Qbix/Platform/tree/main/platform/classes/...
PS: If you do use a relational database for storing graph data, you're going to have a lot of duplication in some public keys. I highly recommend putting ZFS underneath, to help with deduplication. ZFS uses zstd, developed at facebook, and also can encrypt your data at rest (don't use the relational database to do the encryption, otherwise deduplication doesn't work).
The feature scores are from a paper cited on the site. The ranking features are proprietary to dissuade gaming but are a blend of open public data across a number of different sources.
I find it funny that all of these little tools lean into the slop = poop dynamic.
I'm building writetrack.dev - a writing signal sdk that helps folks understand proof of process. It takes a different approach to writing analysis and I'm pretty sure the logo will never feature a brown turd.
https://garphield.com as seen on https://gdb-engines.com/graph/query-languages/
reply