Earlier quoted context omitted.
...turns out they are compared here: https://docs.latticedb.org/comparisons/vs-kuzu
Congrats! For those into the `pip install ...` flow and kuzu, is gfql: we started around the same time in a non-VC-funded oss manner with overlap in key architectural ideas: - cpu columnar vectorized engine + optionally the only open source gpu engine mode for bigger graphs / faster queries - removes the need for a database / file: pure compute-tier engine you can write to parquet/json if you want, plays with paralle…
Show HN: LatticeDB – Like SQLite but for graph databases
51–54 of 54 posts
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#52Nice work. How do you handle concurrent writers on a single file? That's where embedded databases usually get tricky, and the graph model makes locking even more interesting.
Just added file locking to avoid concurrent writers across processes in the latest release.
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#53Earlier quoted context omitted.
Congrats! For those into the `pip install ...` flow and kuzu, is gfql: we started around the same time in a non-VC-funded oss manner with overlap in key architectural ideas: - cpu columnar vectorized engine + optionally the only open source gpu engine mode for bigger graphs / faster queries - removes the need for a database / file: pure compute-tier engine you can write to parquet/json if you want, plays with paralle…
this one? https://pygraphistry.readthedocs.io/en/latest/gfql/index.htm...
Yep!
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#54How does it compare to embedded SurrealDB?