Show HN: LatticeDB – Like SQLite but for graph databases

The permissions question is interesting. I think the answer depends on context. One approach would be to create some edge types `hasAccessTo` and `accessibleBy` that connect a user to a node. Then I'd create an edge type `childOf`. The rest is business logic. Permission checks can just traverse up to the first root node with permissions. The downside is this is all business logic, so can't really look at the database and understand this is how it works. Depending on the database you could create a function that returns permissions for any node, that encapsulates this logic.

Anyways, thanks for checking it out! Really appreciate it. Good luck with your project!

I am in the final stages of adding this based on your comment. Just wrapping up doc updates and will push a new release with hot copy functionality tonight!

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 parallel reader/writers in simple ways b/c that, and TBD iceberg

- adds full graph analytic pipeline support, eg, for feature engineering in real-time fraud & memory pipelines

- also millisecond/submillisecond times on small graphs like that small 100K edge graph benchmark

Main box not formally checked is streaming. Funny enough, we're designed for GPU firehose workloads, so would be fun to demo and see what gaps are left.

LadybugDB maintainer here.

Couple of corrections:

* LadybugDB has revamped the Kuzu WAL design. It shouldn't be hard to build WAL based replication

* 19ms vs 39us - like the author says these are vastly different systems and the benchmark methodology may not be comparable.

We've mostly focused on query plan optimizations, not so much the micro query operator optimizations.

The 0.20.x end of the month release should have some interesting optimizations.

  * Prepared statements will cache query plans and result vectors. So you don't pay malloc costs
  * SIMD optimizations for filter. More to come in the next release.