Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: LatticeDB – Like SQLite but for graph databases

github.com

Post reply on HN
Print view View original

21–30 of 55 posts

Re: Show HN: LatticeDB – Like SQLite but for graph databases

#21

Post by smiths1999 »

nrjames wrote: post #19

Out of curiosity, why did you not fork and build on Kuzu?

Great question! Two reasons. One, I wanted to build something on my own from the ground up rather than contribute to an already established large project. For me, it's a better way to learn. Hopefully people find it cool and want to use it. But if the best that happens is it's just a fun project I built then that is just fine for me. Secondly, the data layouts are different. They are very similar in the single-file, graph db respect. But lattice is transactional and row oriented while kuzu is columnar.

Re: Show HN: LatticeDB – Like SQLite but for graph databases

#23

Post by k9294 »

I'm a big fan of SQLite embedded nature, which allows for chaining multiple SQL calls with near-zero latency.

I'm currently building a personal knowledge graph server a mix of Notion's custom entities via JSON schema and Obsidian markdown+backlinked references. It's working well, but I suspect your product might be a better fit.

I do have one question regarding permissions: how would you recommend modeling a hierarchical access system in a graph database? Specifically, if a user is granted access to a document, they should automatically have access to all its child documents within that workspace. Is there a standard way to model this 'subtree' permission logic, or perhaps a more efficient approach you'd suggest?

Really impressed with the product good luck with it!

Re: Show HN: LatticeDB – Like SQLite but for graph databases

#27

Post by zvr »

smiths1999 wrote: post #17
tomComb wrote: post #15

I wonder about mapping RDF data (like Wikidata) to this. I guess the RDF predicate becomes the edge in your node-edge style of graph.

Yes! This is something I've been thinking about quite a bit the past few weeks. We are going in this direction at work and I think graph storage is a natural way to think about this.

If you're going to support RDF, please also consider supporting SPARQL for querying the data.
Post reply on HN