21–30 of 68 posts
Link to kuzudb internals: https://kuzudb.com/docs/developer-guide/database-internal/
Abandoned for a new project. Kuzu is Japanese for unwanted/useless scraps or garbage, so I suppose it's still living up to its name.
Oh too bad. Small fast embedded graph DBs are rare. Any good alternatives?
Earlier quoted context omitted.
The fact that GQL is now supported by some of the relational Database, doesn't mean they'll become an alternative to native Graph Databases.
Yeah I guess it’s like saying that relational DBs supporting native JSON type meant the end of NoSQL DBs.
This holds true for 95% of cases of well-made software.
https://duckdb.org/community_extensions/extensions/duckpgq.h...
https://adsharma.github.io/beating-the-CAP-theorem-for-graph...
I use the Python Kuzu graph database library, super convenient for local experiments. I see no reason to stop using it. The underlying database is archived on GitHub so it isn’t going anywhere.
Last few releases, you couldn't open a file written by a previous version of kuzu. You had to constantly export/import as new versions were released.
This is no longer a problem for kuzu because development has stopped. But any open source fork needs to think about how to stabilize storage.
In the past few releases kuzu switched from database as a directory to a single file database.