LatticeDB

Data

embedded graph database

SHOW HN2026

190points
54comments
#317of 4,366 in 2026
Top 8%of 2026 by points

How HN took it

CuriousMostly questions and neutral comments

5 positive, 10 neutral or asking, 0 mixed, 1 critical, out of 16 comments about the project. Thread score +0.20.

Docs: 2 for, 0 againstIdea: 1 for, 0 againstPerformance: 0 for, 1 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Excellent README and clear 'when to use / not use' section

    From 2 comments
    • Very nice - been looking for something that combined the flexibility of graph DBs like Neo4j with the simplicity and low cognitive overhead of SQLite. PErformance looks great…
      anigbrowl on HN
    • Just read through the README on GitHub and this looks impressive! Kudos
      ebb_earl_co on HN
  • Sqlite-like embedded design is appealing

    From 2 comments
    • 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…
      k9294 on HN
    • Thank 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…
      vorpalhex on HN
  • Clean, visually appealing docs site

    From 1 comment
    • I like the aesthetics of this page. Very clean and visually appealing
      smiths1999 on HN

Objections

  • Benchmark numbers differ from the README and comparison site

    From 1 comment
    • I measured this on a M4 mac mini (base model): ``` zig build sqlite-benchmark Medium (100K nodes) +----------------------+-----------+---------+---------+ | Workload | LatticeDB…
      adsharma on HN
  • Built with LLMs; tests may be superficial

    From 1 comment
    • I did some perf benchmarking with 1M nodes but I'm mostly using it at smaller scales for another project exploring agentic memory. Most interesting part is a tough one. From a…
      smiths1999 on HN
  • Lacked cross-process locking; concurrent writers unsafe

    From 1 comment
    • Nice 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.
      vladigtr on HN

Requests

  • Litestream-style backup or hot copy

    From 1 comment
    • Does it have something like litestream to backit up for specific production usecases (i.e. a single webserver is enough and downtime of a few mins is tolerable)?
      itissid on HN
  • RDF and SPARQL support

    From 2 comments
    • 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.
      tomComb on HN
    • If you're going to support RDF, please also consider supporting SPARQL for querying the data.
      zvr on HN
  • Hierarchical permission modeling examples

    From 1 comment
    • 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…
      k9294 on HN

Questions

  • How does it compare to KuzuDB, LadybugDB, DuckPGQ, SurrealDB?

    From 4 comments
    • Out of curiosity, why did you not fork and build on Kuzu?
      nrjames on HN
    • LatticeDB looks good, just curious how useful is duckpgq https://duckdb.org/community_extensions/extensions/duckpgq
      srameshc on HN
    • How does it compare to embedded SurrealDB?
      pwmglenn on HN
    • See also: https://ladybugdb.com/ "DuckDB for graphs"
      anentropic on HN
  • How concurrent writers and multi-process access are handled

    From 2 comments
    • Nice 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.
      vladigtr on HN
    • Nice! 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?
      soumitsrah on HN
  • How much of the code was written with Claude

    From 1 comment
    • I see "Claude" listed as a contributor. Could you describe how and how much? I'm keen to see how this looks in practise. As for the tool, it scratches an itch I've been having,…
      tescreal on HN

Alternatives named

  • Kuzu / LadybugDB

    From 2 comments
    • See also: https://ladybugdb.com/ "DuckDB for graphs"
      anentropic on HN
    • ladybugdb ( https://github.com/LadybugDB/ladybug ) appears to be an open source successor to Kuzu fwiw
      ble on HN
  • DuckPGQ

    From 1 comment
    • LatticeDB looks good, just curious how useful is duckpgq https://duckdb.org/community_extensions/extensions/duckpgq
      srameshc on HN
  • SurrealDB

    From 1 comment
  • ArcadeDB

    From 1 comment
    • Why don't just use ArcadeDB (https://arcadedb.com)? Its Graph OLAP makes graph queries faster than KuzuDB (LadybugDB now).
      lvca on HN
  • Neo4j

    From 1 comment
    • Very nice - been looking for something that combined the flexibility of graph DBs like Neo4j with the simplicity and low cognitive overhead of SQLite. PErformance looks great…
      anigbrowl on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/49437049)