Show HN: Simple-graph – a graph database in SQLite
1–10 of 44 posts
Re: Show HN: Simple-graph – a graph database in SQLite
#2How does this perform compared to a “native” graph database like Neo4J?
Re: Show HN: Simple-graph – a graph database in SQLite
#3How does this perform compared to a “native” graph database like Neo4J?
Isn't it like asking "how does sqlite perform compared to databases like PostgreSQL" ?
SQLite is used a lot on edge (mobile apps, ...), sounds like this project provide a graph database for the very same use case (I probably won't run Neo4J on mobile).
Re: Show HN: Simple-graph – a graph database in SQLite
#4How does this perform compared to a “native” graph database like Neo4J?
Isn't it like asking "how does sqlite perform compared to databases like PostgreSQL" ? SQLite is used a lot on edge (mobile apps, ...), sounds like this project provide a graph database for the very same use case (I probably won't run Neo4J on mobile).
IMO it’s a different question. SQLite and Postgres are both relational databases, it stands to reason that they’re at least doing things in similar ways. They’re two implementations of the same idea(ish). A graph database is something else altogether. Grafting that capability onto a relational database has the potential to perform horribly.
It’s a bad analogy, but SQLite to Postgres is like AMD vs Intel x86 CPUs, whereas a graph database is ARM. Can it be emulated? Yes. Is there a far greater potential for slowdown? Yes.
Re: Show HN: Simple-graph – a graph database in SQLite
#5How does this perform compared to a “native” graph database like Neo4J?
Isn't it like asking "how does sqlite perform compared to databases like PostgreSQL" ? SQLite is used a lot on edge (mobile apps, ...), sounds like this project provide a graph database for the very same use case (I probably won't run Neo4J on mobile).
Then maybe no such questions are necessary.
Re: Show HN: Simple-graph – a graph database in SQLite
#6How does this perform compared to a “native” graph database like Neo4J?
Isn't it like asking "how does sqlite perform compared to databases like PostgreSQL" ? SQLite is used a lot on edge (mobile apps, ...), sounds like this project provide a graph database for the very same use case (I probably won't run Neo4J on mobile).
I think the big difference here is that when comparing SQLite you are at least using the same query language.
In the graph space you have Gremlin, Cryper, GQL and many other proprietary query engines (which also looks to be the the case here).
Without that accessibility this feels a bit like pickling a NetworkX object.
Re: Show HN: Simple-graph – a graph database in SQLite
#7Why not add that functionality directly to SQLite via stored procs*
https://www.amazon.com/Hierarchies-Smarties-Kaufmann-Managem...
Re: Show HN: Simple-graph – a graph database in SQLite
#8Why not add that functionality directly to SQLite via stored procs* https://www.amazon.com/Hierarchies-Smarties-Kaufmann-Managem... * https://github.com/wolfch/sqlite-3.7.3.p1
[deleted]
Re: Show HN: Simple-graph – a graph database in SQLite
#9How does this perform compared to a “native” graph database like Neo4J?
Neo4j has failed queries I have written, with "out of memory" errors. I have never, ever, ever gotten that from SQLite.
Re: Show HN: Simple-graph – a graph database in SQLite
#10Tangentially related to graph dbs, but if you're looking for more hierarchical support, SQLite does has a transitive closure extension[0] that might be of some assistance. I leveraged this back in 2014 to write our framework-agnostic result storage on AWS Device Farm.
[0] - https://www.sqlite.org/cgi/src/artifact/636024302cde41b2bf0c...
[1] - https://charlesleifer.com/blog/querying-tree-structures-in-s...