Show HN: LatticeDB – Like SQLite but for graph databases
github.com
Show HN: LatticeDB – Like SQLite but for graph databases
1–10 of 54 posts
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#2Re: Show HN: LatticeDB – Like SQLite but for graph databases
#3What are some of the scales of the data you've been able to test this design on so far?
What was the most interesting part of designing it for you?
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#4Re: Show HN: LatticeDB – Like SQLite but for graph databases
#5Re: Show HN: LatticeDB – Like SQLite but for graph databases
#6See also: https://ladybugdb.com/ "DuckDB for graphs"
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#7Re: Show HN: LatticeDB – Like SQLite but for graph databases
#8Thank you for sharing. I think the sqlite-esque local file approach makes sense for a lot of use cases. What are some of the scales of the data you've been able to test this design on so far? What was the most interesting part of designing it for you?
Most interesting part is a tough one. From a learning perspective the beginning was incredibly interesting because I was spending a lot of time learning about how other DBs work. Even something as relatively simple as writing to disk had a lot more complexity to it than I initially anticipated.
I used LLMs extensively in building this, and the other interesting part was seeing how they failed. I've always been a proponent that tests are no guarantee of quality code, and working with LLMs has only reinforced it. They often write superficial tests. Sometimes a suite of tests would pass, but when I would actually play around with the feature it was clearly broken. LLMs certainly enabled me to build something of this scope, but it was far from "build a graph DB and notify me when you are done"
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#9See also: https://ladybugdb.com/ "DuckDB for graphs"