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–60 of 62 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?
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#55How does it compare to embedded SurrealDB?
Not comparable. Similar to Neo4j vs LatticeDB. Lattice's goals are simplicity, single file, super easy to start using. Surreal supports embedded mode, but my understanding is it is not a single file. Surreal supports a huge number of data models, Lattice is more focused. Surreal also appears to have a company behind it. Lattice is just me.
If you are looking for something lightweight and simple, choose Lattice. If you are an Enterprise looking for hosting, Enterprise support, and maybe a database that can handle all of your needs instead of a specific one, pick SurrealDB.
I hadn't heard of SurrealDB until your comment though, so take what I have to say here with a grain of salt.
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#56See also: https://ladybugdb.com/ "DuckDB for graphs"
Ladybug looks promising after KuzuDB was sunset (acquired by Apple). However, I really miss the content posted by the KuzuDB team on their YouTube channel.
https://www.youtube.com/@ladybugdb - what content would you like to see?
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#57Nice! I am a huge fan of using process-embedded DBs. Question though: how are you dealing with multi-process access? or does 1 process lock the db?
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#58Why don't just use ArcadeDB (https://arcadedb.com)? Its Graph OLAP makes graph queries faster than KuzuDB (LadybugDB now).
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#59Why don't just use ArcadeDB ( https://arcadedb.com )? Its Graph OLAP makes graph queries faster than KuzuDB (LadybugDB now).
Why not use something else? I wanted to build something from scratch.
What you've built with ArcadeDB is definitely impressive, but much larger scale that what I was trying to accomplish with this. Like the repo says, think sqlite but for graph dbs :)
Re: Show HN: LatticeDB – Like SQLite but for graph databases
#60Nice! I am a huge fan of using process-embedded DBs. Question though: how are you dealing with multi-process access? or does 1 process lock the db?
Answered elsewhere but the tl;dr is lock the db file. The design is multiple readers, single writer.