Simple-graph: a graph database in SQLite, via “SQLite as a document database”

• rdflib-sqlalchemy

  2 145 5.6 Python

  RDFLib store using SQLAlchemy dbapi as back-end

  

https://github.com/RDFLib/rdflib-sqlalchemy

It also persists namespace mappings so that e.g. schema:Thing expands to http://schema.org/Thing

The table schema and indices are defined in rdflib_sqlalchemy/tables.py:

• ipfs-sqlite-block-store

  1 44 0.0 Rust

  SQLite based ipfs block store (by Actyx)

  

Interesting. SQLite is awesome.

I did something similar recently, a block store for a rust implementation of ipfs, which models a directed acyclic graph of content-addressed nodes.

https://github.com/actyx/ipfs-sqlite-block-store

I found that performance is pretty decent if you do almost everything inside SQLite using WITH RECURSIVE.

The documentation has some really great examples for WITH RECURSIVE. https://sqlite.org/lang_with.html

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• graphdb

  1 184 0.0 Python

  sqlite based graph database for storing native python objects and their relationships to each other

Similar project: https://github.com/CodyKochmann/graphdb

• simple-graph

  7 1,329 2.5 Go

  This is a simple graph database in SQLite, inspired by "SQLite as a document database"

• sqlite-3.7.3.p1

  1 19 0.0 C

  SQLite with stored procedures

Why not add that functionality directly to SQLite via stored procs*

*https://github.com/wolfch/sqlite-3.7.3.p1

• sqlite3-bfsvtab-ext

  2 17 0.0 C

  A virtual table extension for breadth-first search queries in Sqlite3

I've actually been working on an extension to perform breadth first search queries in SQLite on general graphs [0]. The extension is actually based off of the transitive closure extension. You can use it on any existing SQLite database as long as you can wrangle your edges into either a real or virtual table and the node ids are integers (I'm planning on removing this constraint in the future).

[0]: https://github.com/abetlen/sqlite3-bfsvtab-ext

• ulid-postgres

  1 30 0.0 PLpgSQL

To some extent I think it depends on what data you're storing in the graph ie. If it's temporal data using a ulid instead of a guid speeds things up significantly (30x for large data) as your ids are not as fragmented.

https://github.com/schinckel/ulid-postgres/blob/master/ulid....

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project